src-test2/usr.sbin/syslogd, branch release/2.2.0 FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F2.2.0 1997-03-14T01:35:16Z YAMFC (rev 1.21) 1997-03-14T01:35:16Z Joerg Wunsch joerg@FreeBSD.org 1997-03-14T01:35:16Z urn:sha1:de653435c9258bef7c7959b2aba7a611edb1c013 YAMFC: 1997-03-06T08:01:10Z Mike Pritchard mpp@FreeBSD.org 1997-03-06T08:01:10Z urn:sha1:a5b108bc51bd1997e5c44253d326c14a5ffda682 - sort xrefs - typo fixes. YAMFC (rev 1.19, and 1.4 resp.: allow piping to subprocess) 1997-03-02T14:59:49Z Joerg Wunsch joerg@FreeBSD.org 1997-03-02T14:59:49Z urn:sha1:d4ded982034d58807a80ab0ceb512c617906dc80 Merge r1.17 from current 1997-01-03T07:24:16Z Jordan K. Hubbard jkh@FreeBSD.org 1997-01-03T07:24:16Z urn:sha1:5dda5c003d96374395d34724f0a191a61ce28b94 YAMFC 1996-12-14T13:57:58Z Joerg Wunsch joerg@FreeBSD.org 1996-12-14T13:57:58Z urn:sha1:6614561c3d7a2876a0fbd0c3d33131654c67ac55 YAMFC 1996-11-28T08:28:35Z Poul-Henning Kamp phk@FreeBSD.org 1996-11-28T08:28:35Z urn:sha1:f72f5a58cc94fe39f63b4c32a564b34b4beb12bb Back out the entire change from rev 1.11 of syslogd.c. It was bogus. 1996-10-28T08:25:13Z Joerg Wunsch joerg@FreeBSD.org 1996-10-28T08:25:13Z urn:sha1:1c0899bbb054ae8220842f2c0e26b8168089b084 Correct the man page to reflect the new reality. Reviewed by: various (mailing list feedback) 1996-10-23T20:17:57Z Julian Elischer julian@FreeBSD.org 1996-10-23T20:17:57Z urn:sha1:36be1f6be985422758260aac919ef741380f1bb0 Submitted by: whistle communications move the socket from /dev to /var/run by default TRANSITIONALLY make syslog add a symlink.. I PROMISE I'll remove that as soon as I have the makefiles etc fixed as well. syslogd has always bugged me with it's async startup at boot time. 1996-10-05T15:20:51Z Peter Wemm peter@FreeBSD.org 1996-10-05T15:20:51Z urn:sha1:4ed8e95bc081536cf5a69c9896da5a2f82c4049f 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. Add info field. 1996-09-27T20:31:26Z Paul Traina pst@FreeBSD.org 1996-09-27T20:31:26Z urn:sha1:3d08ec926a78bc612251b0136c4cc9b304bbaec7 Closes pr docs/1679.