From owner-freebsd-questions Sat Jun 1 9:40:47 2002 Delivered-To: freebsd-questions@freebsd.org Received: from infinity.aesredfish.net (ns1.aesredfish.net [65.168.0.12]) by hub.freebsd.org (Postfix) with ESMTP id 46CCB37B401 for ; Sat, 1 Jun 2002 09:40:42 -0700 (PDT) Received: from potentialtech.com (mhope-dhcp-65-168-1-181.dashfast.com [65.168.1.181]) by infinity.aesredfish.net (8.11.6/8.11.0) with ESMTP id g51GcbU10026; Sat, 1 Jun 2002 12:38:38 -0400 Message-ID: <3CF8F9EC.1080908@potentialtech.com> Date: Sat, 01 Jun 2002 12:44:28 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020502 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Len Conrad Cc: freebsd-questions@freebsd.org Subject: Re: newsyslog + BIND 9.2.1 more details References: <5.1.0.14.2.20020601061449.053d2eb8@mail.Go2France.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Len Conrad wrote: > BIND 9.2.1 + FreeBSD 4.5-Rel > > named.run is rotated out and named.run.0 is created. > > named.run.0 not gzipped to named.run.0.gz Send you syslog.conf file so we can check it for errors. > named.run is created and contains just > > Jun 1 00:00:00 montwood newsyslog[4830]: logfile turned over named doesn't log this, newsyslog does. > but not other named logging > > killall -HUP syslogd Are you logging through syslogd or is named logging directly to the file? If you're not logging through syslogd, restarting it isn't going to help anything. > ... doesn't get the named loggind running again, but > > killall -HUP named > > ... does work. Read the docs. This is very common. Many daemons won't release their file descriptor on the first file, and even though it's been renamed, they're trying to log to it still. That's why syslog has the last field in the syslog.conf file, that tells it to send a HUP signal to a certain process ID, thus forcing the process to redo its file descriptors, and attach to the correct log file. Read "man syslog.conf". It will explain this. > We are also having trouble with newsyslog not rotating Apache logs. Same issue. Enter the proper pid file in newsyslog.conf and Apache will be restarted so it logs to the correct file. -- Bill Moran Potential Technology http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message