From owner-freebsd-current Fri Jan 19 3:33:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2A1E737B400; Fri, 19 Jan 2001 03:32:58 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA52701; Fri, 19 Jan 2001 12:32:54 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname References: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> From: Dag-Erling Smorgrav Date: 19 Jan 2001 12:32:53 +0100 In-Reply-To: cjclark@reflexcom.com's message of "Thu, 18 Jan 2001 19:30:25 -0800 (PST)" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message