Peter Wemm 4ed8e95bc0 syslogd has always bugged me with it's async startup at boot time. ... For me, more often than not, the backgrounded syslogd daemon is not yet ready to process log messages before other things (such as named) want to log a heap of them. It seems that it's the O_SYNC writes of the stuff coming in from /dev/klog that's the slowdown. Anyway, instead of using the libc daemon, roll a modified version. This one has a timeout. The child will wait for either the timeout to expire or the child process to signal it to let it know that it's "ready" and the /dev/log socket is set up and active, so it's safe to continue the boot. It adds a small fraction of a second pause to the boot time, but on the other hand the overall boot time is *quicker* since the disk is not being thrashed while the log messages are getting written out synchronously one by one while other daemons are loading in parallel. The timeout is in case the child segfaults or something before becoming fully operational.		1996-10-05 15:20:51 +00:00
..
Makefile	Get rid of update. Make man page installation work with our scheme	1994-08-05 16:31:05 +00:00
pathnames.h	BSD 4.4 Lite usr.sbin Sources	1994-05-26 05:23:31 +00:00
syslog.conf.5	Add info field.	1996-09-27 20:31:26 +00:00
syslogd.8	Bring in some fixes from NetBSD and re-hack our syslogd to be option-compatible	1996-07-22 16:35:50 +00:00
syslogd.c	syslogd has always bugged me with it's async startup at boot time.	1996-10-05 15:20:51 +00:00