From owner-freebsd-security  Fri Mar  9  1:54:16 2001
Delivered-To: freebsd-security@freebsd.org
Received: from gyw.com (gyw.com [209.55.67.177])
	by hub.freebsd.org (Postfix) with ESMTP id 0BC1D37B71A
	for <freebsd-security@FreeBSD.ORG>; Fri,  9 Mar 2001 01:54:08 -0800 (PST)
	(envelope-from tjk@tksoft.com)
Received: from uno.tksoft.com (smtp3.tksoft.com [192.168.50.56] (may be forged))
	by as.tksoft.com (8.8.8/8.8.8) with ESMTP id DAA16350;
	Thu, 8 Mar 2001 03:31:16 -0800
Received: (from tjk@tksoft.com)
	by uno.tksoft.com (8.8.8/8.8.8) id DAA28826;
	Thu, 8 Mar 2001 03:11:24 -0800
From: "tjk@tksoft.com" <tjk@tksoft.com>
Message-Id: <200103081111.DAA28826@uno.tksoft.com>
Subject: Re: ipmon via syslog
To: craig@allmaui.com (Craig Cowen)
Date: Thu, 8 Mar 2001 03:11:23 -0800 (PST)
Cc: tjk@tksoft.com (tjk@tksoft.com),
	freebsd-security@FreeBSD.ORG (freebsd-security@FreeBSD.ORG)
In-Reply-To: <3AA75B26.B2C62001@allmaui.com> from "Craig Cowen" at Mar 08, 2001 02:12:54 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

It depends.

You might have a cron entry for rotating logs with "newsyslog." In
that case you could specify the daemon to send a signal to, in the
/etc/newsyslog.conf file.

The /etc/newsyslog.conf has lines like this:

/var/log/ipf.log  664  3  5000  604800  Z  /var/run/syslog.pid 

This would send a HUP signal to syslog when the logs are rotated.
(at 5 Mb, not more often than once a week). 


Troy



> 
> That dosen't seem reasonable.
> are you saying that I need to know when it roles over and then manually
> restart syslogd?
> 
> I am starting ipmon on boot up via
> 
> ipmon -s -a -D
> 
> 
> my syslog.conf has this line:
> 
> local0.*                                                /var/log/ipf.log
> 
> newsyslog.conf:
> 
> /var/log/ipf.log                        600  40    1024 *    Z
> /var/run/ipmon.pid
> 
> 
> 
> "tjk@tksoft.com" wrote:
> 
> > You need to restart (or send a HUP to) syslogd.
> >
> > Other applications which generate log entries (and don't
> > go through syslogd), might need their own restarts. E.g.
> > httpd.
> >
> > /etc/syslog.conf tells you the syslogd controlled files.
> >
> > Troy
> >
> > >
> > > When ever my log roles over there is a four hour lag.
> > > That is, no logging for the first four hours of the new log file.
> > >
> > > Any suggestions?
> > >
> > >
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-security" in the body of the message
> > >
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message