|
From: Michele P. <10...@ti...> - 2007-03-13 18:53:29
|
At 10.45 13/03/2007 -0700, you wrote: >One other item I noticed. >I use a different firewall than the ones provided (don't know if this >matters here). > >When networking is started, network communications are blocked (all >packets dropped). Starting up the firewall opens up the network (as much >as the firewall allows). >This is fine, since it closes a security hole during boot. > >However, syslog is started BEFORE the firewall is brought up. If you are >logging to a remote system, it, of course, fails since it can't connect. >The workaround for that is to change the order of startup to have syslog >start after the firewall is set up. > >Philip Thank you Philip! You gave me a possible (and quite plausible!!) reason for a remote syslog failure I was having some time ago (at that time I decided to syslog locally instead and put a cron job to tar.gz /var/log/messages every 15 minutes). Tomorrow I'll try your suggestion! If it works I owe you an ale! ^_^ (If you ever pass by) Live long and prosper! (and keep pushing the button! [ 4 8 15 16 23 42 EXECUTE ]) Michele |