Re: Sysklogd 1.3 and later kernels

Wingerde van GR (gertjan@cs.vu.nl)
Wed, 1 May 1996 09:03:47 +0200 (MET DST)

Brian Raymond Doherty writes:
>
> 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?
>

I have the same behaviour here. I think it was introduced with 1.3.94-.
But it could be 1 or 2 patches earlier.

Gertjan

-- 


	Gertjan van Wingerde			home address:
	Student Computer Science
	Vrije Universiteit			J.H. Dunantstraat 44
	Amsterdam                      		1561 BD  Krommenie
	The Netherlands


	e-mail: gertjan@cs.vu.nl
	URL: http://www.cs.vu.nl/~gertjan/