to u+rwx to make our chances of success better. The modes for directories
are reset at the end of a sup run, so we don't need to worry about that.
This possibly might mess up the mode of the parent of the top-level dir,
if the top-level changed to a non-directory. This is probably rare enough
not to care too much about.
XXX: Should probably chmod the containing directory for each non-directory
removal as well, so there wouldn't be complaints about them. Please feel
free to send in your opinions on that...
his last.<collection> list, this directory did not get removed in the client
since the code just tried rmdir(foo) and gave up when that failed. This
has been changed to be more agressive and do an rm -fr when rmdir fails.
it to "."
- include sockio.h if needed to define SIOCGIFCONF (for svr4)
- use POSIX signals and wait macros
- add -S silent flag, so that the client does not print messages unless there
is something wrong
- use flock or lockf as appropriate
- use fstatfs or fstatvfs to find out if a filesystem is mounted over nfs,
don't depend on the major() = 255 hack; it only works on legacy systems.
- use gzip -cf to make sure that gzip compresses the file even when the file
would expand.
- punt on defining vsnprintf if _IOSTRG is not defined; use sprintf...
To compile sup on systems other than NetBSD, you'll need a copy of daemon.c,
vis.c, vis.h and sys/cdefs.h. Maybe we should keep those in the distribution?
erh