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
>
>
>
> "tjktksoft.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 majordomoFreeBSD.org
> > > with "unsubscribe freebsd-security" in the body of the message
> > >
>
>
> To Unsubscribe: send mail to majordomoFreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
>

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

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]