|
From: Bruce S. <bw...@ar...> - 2007-03-13 17:56:28
|
> > 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. > > I'm fine with doing this change if nobody else has a complain about it. I agree that syslog (and all other network services that I can think of) should be started after the firewall. - BS |