| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
value < 0. errno is only updated in this case. Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
|
|
|
|
|
|
| |
as well in order to be able to do stat(1) on the lock file
ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The files needed to be unveiled directly or indirectly via libutil are the
following:
- _PATH_MASTERPASSWD_LOCK - write/create permissions
- _PATH_MASTERPASSWD - read permission
- _PATH_BSHELL - execute permission
- _PATH_PWD_MKDB - execute permission
_PATH_MASTERPASSWD gets read and then _PATH_MASTERPASSWD_LOCK is created and
the content of the former is written on the latter. After this _PATH_BSHELL
spawns an EDITOR (vi(1) by default) and at the end then _PATH_PWD_MKDB is ran
to update the _PATH_MASTERPASSWD based in what was actually changed in
_PATH_MASTERPASSWD_LOCK.
OK deraadt@
|
|
|
|
| |
from Matthew Martin
|
|
|
|
| |
ok mestre
|
|
|
|
|
| |
default case to have usage() explaining that)
- Replace exit(3) with return to enable SSP
|
|
|
|
|
|
| |
remove some references to differences between versions 6 and 7.
ok jmc, millert, tedu
|
| |
|
|
|
|
|
| |
"and" and "or" to join sentence clauses, and you can use commas, but both hinders
reading;
|
|
|
|
|
|
|
|
|
|
| |
Since _PATH_MASTERPASSWD_LOCK is on a local file system in any sane setup
and written to in blocking mode, i don't see how write(2) could return
before having written everything, so this maybe wasn't an actual bug,
but it should be repaired anyway, if only for clarity and extra safety.
From Ben Cornett <ben at lantern dot is>;
ok millert@.
|
|
|
|
| |
struct timeval. OK guenther@
|
|
|
|
|
|
|
| |
unmaintainable). these days, people use source. these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
|
|
|
|
|
|
|
| |
least document /etc/ptmp;
while i'm at it, might as well tidy it up and make it consistent across
these pages;
|
|
|
|
|
|
| |
where the "no changes" case was not properly detected due to timespec
supporting nanosec resolution but timeval only supporting microsec
resolution. OK deraadt@
|
| |
|
| |
|
| |
|
|
|
|
| |
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
|
|
|
|
|
| |
edit, just stash it once in copyfile(). This fixes the check for
whether or not changes have been made (based on the timestamp) for
cases like when the _shadow group is missing but is fixed by the
admin during the next edit.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
o when copying to temp file set utimes on temp file equal to original
o use st_mtimespec instead of st_mtime for better granularity
|
| |
|
|
|
|
| |
specify a username (and thus avoid rebuilding the while database).
|
|
|
|
| |
cleanup along the way.
|
|
|
|
|
| |
was changed during edit. Crontab patch from <andrew@untraceable.net>.
It may be better to simply do a real compare inline.
|
|
|
|
| |
is used instead; kwesterback@home.com
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|