Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 08 Mar 2001 03:16:37 -0800
From:      Craig Cowen <craig@allmaui.com>
To:        "tjk@tksoft.com" <tjk@tksoft.com>
Cc:        "freebsd-security@FreeBSD.ORG" <freebsd-security@FreeBSD.ORG>
Subject:   Re: ipmon via syslog
Message-ID:  <3AA76A15.44C9BB29@allmaui.com>
References:  <200103081111.DAA28826@uno.tksoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your help.
Do you see any problems with my current setup as outlined below?

"tjk@tksoft.com" wrote:

> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AA76A15.44C9BB29>