From owner-freebsd-questions Sat Nov 8 10:50:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18386 for questions-outgoing; Sat, 8 Nov 1997 10:50:18 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA18381 for ; Sat, 8 Nov 1997 10:50:15 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA27421; Sat, 8 Nov 1997 10:41:10 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd027418; Sat Nov 8 10:41:02 1997 Date: Sat, 8 Nov 1997 10:39:13 -0800 (PST) From: Julian Elischer To: Sheldon Hearn cc: freebsd-questions@FreeBSD.ORG Subject: Re: syslogd doesn't read syslog.conf on HUP In-Reply-To: <25817.879004059@axl.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk sounds to me like you just volunteered to become an expert on syslogd. send patches :) On Sat, 8 Nov 1997, Sheldon Hearn wrote: > > Hi folks, > > I was lead to believe that syslogd would reconfigure itself on receipt > of a HUP signal (1). I thought this included rereading the syslog.conf > file. Here's the part of the syslogd(8) manpage that led me to believe > this: > > Syslogd reads its configuration file when it starts up and whenever > it receives a hangup signal. For information on the format of the > configu- ration file, see syslog.conf(5). > > I've tested this on my FreeBSD 2.2-STABLE (5 Nov 1997) box as well as my > FreeBSD 2.2.2-RELEASE box and on both machines it appears that syslogd > does _not_ reread syslog.conf on receipt of a HUP. The process must be > killed and restarted. > > Is the manpage out of date, or is syslogd not doing its job? > > Sheldon. >