Date: Sat, 8 Nov 1997 10:39:13 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Sheldon Hearn <axl@iafrica.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: syslogd doesn't read syslog.conf on HUP Message-ID: <Pine.BSF.3.95.971108103733.3896B-100000@current1.whistle.com> In-Reply-To: <25817.879004059@axl.iafrica.com>
next in thread | previous in thread | raw e-mail | index | archive | help
sounds to me like you just volunteered to become an expert on syslogd. send patches :) On Sat, 8 Nov 1997, Sheldon Hearn wrote: > > Hi folks, > > I was lead to believe that syslogd would reconfigure itself on receipt > of a HUP signal (1). I thought this included rereading the syslog.conf > file. Here's the part of the syslogd(8) manpage that led me to believe > this: > > Syslogd reads its configuration file when it starts up and whenever > it receives a hangup signal. For information on the format of the > configu- ration file, see syslog.conf(5). > > I've tested this on my FreeBSD 2.2-STABLE (5 Nov 1997) box as well as my > FreeBSD 2.2.2-RELEASE box and on both machines it appears that syslogd > does _not_ reread syslog.conf on receipt of a HUP. The process must be > killed and restarted. > > Is the manpage out of date, or is syslogd not doing its job? > > Sheldon. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.971108103733.3896B-100000>