syslogd hoses up the system

[Erik Andersen]

Package: busybox
Version: 0.50

When running busybox syslogd from init, it appears that syslogd is now
blocking, which causes its parent (init) to block, causing all sorts of bad
behavior (reboot doesn't work since signals are delayed, dhcpcd gets blocked
since it tries to log stuff, new apps are not spawned by init, etc).  Once
someone does an openlog() without an immediate closelog(), it seems that
syslogd starts blocking other clients. 

This was demonstrated to me using busybox 0.50, busybox running as init, and
where /etc/init.d/rcS called a script to start syslogd and klogd, then went on
to start some other stuff.  Then, logging in at the shell and running dhcpcd,
or reboot was sufficient to see the problem.

 -Erik

--
Erik B. Andersen   email:  andersen at lineo.com
--This message was written using 73% post-consumer electrons--

---------------------------------------
Received: (at 1138-done) by bugs.lineo.com; 3 Apr 2001 17:08:23 +0000