-----BEGIN PGP SIGNED MESSAGE-----
With later kernels (i.e. since the '70s or '80s) for some bizarre reason,
syslogd will not start up correctly. In my rc.inet2 I have:
# Start the SYSLOGD/Klogd daemons. These must come first.
if [ -f ${NET}/syslogd ]; then
echo -n " syslogd"
${NET}/syslogd
echo -n " klogd"
${NET}/klogd
fi
where NET is defined as /usr/sbin, where I keep the executables. Syslogd
and klogd appear to start-up as usual, but by the time I get to a prompt,
only klogd is running. Then, if I run /usr/sbin/syslogd as root, it runs
and stays running. Adding the -d option to syslogd at the command line
produces no error messages, while doing it in rc.inet2 has no effect.
Does anyone know what's wrong? Is this related to the named pipes change
that broke SysVInit?
B
- ---------------------------------------------------------------------------
Brian R. Doherty | "You know, I bet a funny thing about driving a
6320 S. Main St. | car off a cliff is, while you're in midair, you
Houston, TX 77006 | still hit those brakes! Hey, better try the
doherty@rice.edu | emergency brake!" -- Jack Handey
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBMYV7AWr8tJOG0vRxAQFRcAP/ev9xOtFQWqf30k/KK4e1cbxW+dykODiW
IcwXBlfZCYtYfW0vZ5+SlHSZvLZSo68sCIzOtCWLkJVhk+Jk3f7GPvwKCKSweLgt
xdiVY7kQIITMZ2OOWtuT5zfMtoWMw/pIL+K/wSkd/xA6ucqfNwNOuKjB7IBpLwzf
Gljzq2fTkac=
=nQDm
-----END PGP SIGNATURE-----