Re: bin/24444: syslogd(8) does not update hostname

2001-01-21 Thread Andrea Campi
the hostname, one being a syscall and the other being a sysctl. One could of course have the kernel print a message to the console about it, syslogd(8) would pick that up. Yes, I was about to propose this, but then I thought: why? If we go this way, then we should definitely also log an IP

Re: syslogd(8) does not update hostname

2001-01-20 Thread Mark Murray
an IP address there. I would be HOPPING mad if that caused my hostname and VPN to break. M Submitter-Id: current-users Originator: Crist J. Clark Organization: Confidential: no Synopsis: syslogd(8) does not update hostname Severity: non-critical Priority

Re: syslogd(8) does not update hostname

2001-01-20 Thread Crist J. Clark
On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote: I don't agree with this change. hostname != name-that-IP-address-resolves-to. Dunno what you are talking about. That has nothing directly to do with this. No one is talking about forcing you to change your hostname. The patch just

Re: syslogd(8) does not update hostname

2001-01-20 Thread Mark Murray
On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote: I don't agree with this change. hostname != name-that-IP-address-resolves-to. Dunno what you are talking about. That has nothing directly to do with this. No one is talking about forcing you to change your hostname. The

Re: bin/24444: syslogd(8) does not update hostname

2001-01-20 Thread Crist J. Clark
On Fri, Jan 19, 2001 at 11:09:24PM +0100, Dag-Erling Smorgrav wrote: "Crist J. Clark" [EMAIL PROTECTED] writes: On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: It should also log a message if the hostname changes. Should that be a responsibility of syslogd(8) or

Re: bin/24444: syslogd(8) does not update hostname

2001-01-20 Thread Dag-Erling Smorgrav
"Crist J. Clark" [EMAIL PROTECTED] writes: How about just logging a sethostname(3) call? Still doesn't help. There are (at least) two different ways of setting the hostname, one being a syscall and the other being a sysctl. One could of course have the kernel print a message to the console

Re: bin/24444: syslogd(8) does not update hostname

2001-01-19 Thread Dag-Erling Smorgrav
[EMAIL PROTECTED] 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

Re: bin/24444: syslogd(8) does not update hostname

2001-01-19 Thread Crist J. Clark
On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: [EMAIL PROTECTED] 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

Re: bin/24444: syslogd(8) does not update hostname

2001-01-19 Thread Dag-Erling Smorgrav
"Crist J. Clark" [EMAIL PROTECTED] writes: On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: It should also log a message if the hostname changes. Should that be a responsibility of syslogd(8) or hostname(1)? I meant syslogd(8), but putting it in hostname(1) might makes

syslogd(8) does not update hostname

2001-01-18 Thread cjclark
Submitter-Id: current-users Originator: Crist J. Clark Organization: Confidential: no Synopsis: syslogd(8) does not update hostname Severity: non-critical Priority: medium Category: bin Release:FreeBSD 5.0-CURRENT i386 Class: sw-bug Environment