Pawel Jakub Dawidek 8b28aef238 Pidfiles should be created with permission preventing users from opening ... them for reading. When user can open file for reading, he can also flock(2) it, which can lead to confusions. Pointed out by: green		2005-09-16 11:24:28 +00:00
..
_secure_path.3
_secure_path.c
auth.3
auth.c
auth.conf.5
fparseln.3
fparseln.c
humanize_number.3
humanize_number.c
libutil.h	Add a family of functions for reliable pidfiles handling.	2005-08-24 17:21:38 +00:00
login_auth.3
login_auth.c
login_cap.3
login_cap.c
login_cap.h
login_class.3
login_class.c
login_crypt.c
login_ok.3
login_ok.c
login_times.3
login_times.c
login_tty.3
login_tty.c
login.3
login.c
login.conf.5
logout.3
logout.c
logwtmp.3
logwtmp.c	NI_WITHSCOPEID cleanup. Neither RFC 2553 nor RFC 3493 defines	2005-05-13 16:31:11 +00:00
Makefile	Add a family of functions for reliable pidfiles handling.	2005-08-24 17:21:38 +00:00
pidfile.3	Pidfiles should be created with permission preventing users from opening	2005-09-16 11:24:28 +00:00
pidfile.c	Add a family of functions for reliable pidfiles handling.	2005-08-24 17:21:38 +00:00
property.3
property.c
pty.3
pty.c
pw_util.c
realhostname_sa.3
realhostname.3
realhostname.c	NI_WITHSCOPEID cleanup. Neither RFC 2553 nor RFC 3493 defines	2005-05-13 16:31:11 +00:00
stub.c
trimdomain.3
trimdomain.c
uucplock.3
uucplock.c