Thanks Dick,
Giving ipmon -Ds flags and directing messages to the
security file using local0.* seems to be the answer.
Specifying a pid file in newsyslog.conf gave errors about
not being able to HUP ipmon.
Cheers,
Gareth
On Fri, 25 Jun 2004 14:24:41 +0100
Dick Davies <[EMAIL PROTECTED]> wrote:
You need to either tell newsyslog the pidfile, so it can HUP
ipmon, or just get it to use syslog (in which case newsyslog
doesn't need to HUP it at all).
* Gareth Bailey <[EMAIL PROTECTED]> [0616 14:16]:
> The -D flag tells it to run as daemon. Starting ipmon with
> ipmon_flags="-D /var/log/securi
The -D flag tells it to run as daemon. Starting ipmon with
ipmon_flags="-D /var/log/security" in rc.conf works fine.
It logs to security as required. The problem comes in when
the /var/log/security file is rotated by newsyslog. After
this occurs, logging stop all together even though ipmon is
still
If you are saying that you have "/sbin/ipmon -D /var/log/security"
on the rc.conf statement, then you are telling it to do 2
conflicting things. The /var/log/security part needs to be removed.
It's telling ipmon to use manual log file after you tell with -d to
use syslog log function.
-Origina
On Fri, Jun 25, 2004 at 02:15:50PM +0200, Gareth Bailey wrote:
> I start ipmon at boot time with "/sbin/ipmon -D
> /var/log/security". Ipmon works fine but seems to stop
> logging entries to the security logfile when it is rotated.
>
> newsyslog.conf sets mode to 700, which should be fine since
>
