From owner-freebsd-questions  Sat Nov  8 07:47:45 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id HAA11980
          for questions-outgoing; Sat, 8 Nov 1997 07:47:45 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA11975
          for <freebsd-questions@freebsd.org>; Sat, 8 Nov 1997 07:47:42 -0800 (PST)
          (envelope-from sheldonh@axl.iafrica.com)
Received: from axl.iafrica.com [196.31.1.167] 
	by lists01.iafrica.com with esmtp (Exim 1.73 #1)
	id 0xUD6a-0002PI-00; Sat, 8 Nov 1997 17:47:24 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: freebsd-questions@freebsd.org
Subject: syslogd doesn't read syslog.conf on HUP
Date: Sat, 08 Nov 1997 17:47:39 +0200
Message-ID: <25817.879004059@axl.iafrica.com>
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


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.