From owner-freebsd-bugs Fri Jan 19 11:10:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3223E37B699 for ; Fri, 19 Jan 2001 11:10:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JJA7v55867; Fri, 19 Jan 2001 11:10:07 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 11:10:07 -0800 (PST) Message-Id: <200101191910.f0JJA7v55867@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Crist J. Clark" Subject: Re: bin/24444: syslogd(8) does not update hostname Reply-To: "Crist J. Clark" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24444; it has been noted by GNATS. From: "Crist J. Clark" To: Dag-Erling Smorgrav Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Date: Fri, 19 Jan 2001 11:03:41 -0800 On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > cjclark@reflexcom.com writes: > > I propose that syslogd(8) should reload the hostname with a > > SIGHUP. I cannot think of any reason that one should not update the > > hostname, but as I pointed out, there are reasons why one would want > > that behavior. > > It should also log a message if the hostname changes. Should that be a responsibility of syslogd(8) or hostname(1)? Personally, it might be a slippery slope to start adding things that syslogd(8) should maintain state on, but since syslogd(8) actually uses the hostname... One also could start arguing that syslogd(8) should check the hostname everytime it logs something despite the performance hit. As for what syslogd(8) does now, if you look at the example output in the PR, notice syslogd(8) didn't even log when it was HUP'ed. IMHO, I think it is beyond the scope of syslogd(8) to actually track changes in the hostname in real-time. Noticing a change when given a HUP signal, would seem reasonable, but if hostname(1) were to log changes, that would also be fairly redundant. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message