Date: Tue, 28 Aug 2001 11:31:01 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: cjclark@alum.mit.edu, Sheldon Hearn <sheldonh@starjuice.net> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c Message-ID: <p0510101bb7b1687f703f@[128.113.24.47]> In-Reply-To: <20010828022238.C442@blossom.cjclark.org> References: <200108272137.f7RLbFP70328@freefall.freebsd.org> <47156.998987939@axl.seasidesoftware.co.za> <20010828022238.C442@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2:22 AM -0700 8/28/01, Crist J. Clark wrote: >On Tue, Aug 28, 2001 at 10:38:59AM +0200, Sheldon Hearn wrote: > > This should probably be noted in the manual page. > >I really didn't see anywhere where the current behavior on a SIGHUP >is too precisely noted. All syslogd(8) says is, > > The syslogd daemon reads its configuration file when it starts > up and whenever it receives a hangup signal. > >Seems odd to over emphisize this one little aspect of a syslogd(8) >reload. I think that this would be what people would expect. IMHO, >the old behavior was buggy. I think it's worth mentioning. Is there any other system where syslogd refreshes it's idea of a hostname? What is there says only that it reads the configuration file, so people would NOT expect it to refresh the hostname. I don't think it needs much said about it, but a few words on it would be reasonable. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0510101bb7b1687f703f>