Changes to /etc/syslog.conf do not take effect until you tell the
syslog task to re-read the conf file. You do that be issuing an HUP
signal to the syslog task. Kill -HUP PID where PID is the task
number from the ps ax command.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Hi there, thanks for the sample rules and help in setting
up IPF.
I have restarted since making the changes to syslogd.conf.
I HUP'd syslogd anyway, still no luck. All ipf logs go to
security and messages!
Can you think of anything else that i might do?
Thanks
Gareth
On Mon, 17 May 2004
On Mon, 2004-05-17 at 13:53, Gareth Bailey wrote:
Hi there, thanks for the sample rules and help in setting
up IPF.
I have restarted since making the changes to syslogd.conf.
I HUP'd syslogd anyway, still no luck. All ipf logs go to
security and messages!
Can you think of anything else
logs to messages AND security
On Mon, 2004-05-17 at 13:53, Gareth Bailey wrote:
Hi there, thanks for the sample rules and help in setting
up IPF.
I have restarted since making the changes to syslogd.conf.
I HUP'd syslogd anyway, still no luck. All ipf logs go to
security and messages!
Can you
On Mon, 2004-05-17 at 14:11, JJB wrote:
Your solution of not using the syslog function does not answer his
question. This is bad advice.
Quoted Can you think of anything else that i might do?
and answered:
Rather use:
ipmon_flags=-Dn /var/log/security
This is not bad advice, I was
Thanks for the advice ;-), changing the ipmon_flags did the
trick.
Regards,
Gareth
On Mon, 17 May 2004 14:39:44 +0200
Nelis Lamprecht [EMAIL PROTECTED] wrote:
On Mon, 2004-05-17 at 14:11, JJB wrote:
Your solution of not using the syslog function does not
answer his
question. This is bad
