Date: Tue, 28 Aug 2001 02:22:39 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: 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: <20010828022238.C442@blossom.cjclark.org> In-Reply-To: <47156.998987939@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Tue, Aug 28, 2001 at 10:38:59AM %2B0200 References: <200108272137.f7RLbFP70328@freefall.freebsd.org> <47156.998987939@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 28, 2001 at 10:38:59AM +0200, Sheldon Hearn wrote:
> On Mon, 27 Aug 2001 14:37:15 MST, "Crist J. Clark" wrote:
>
> > Modified files:
> > usr.sbin/syslogd syslogd.c
> > Log:
> > Gives syslogd(8) the ability to refresh its idea of the hostname of
> > the system on which it is running. The hostname is reloaded when
> > 'HUPped' and a log message generated to note a change (before anyone
> > points it out, this is not an added security feature).
>
> Nice one!
>
> 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 plan on doing some more syslogd(8) work. I'll look at the manpages
as a whole during that time.
--
Crist J. Clark cjclark@alum.mit.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?20010828022238.C442>