Tom Eastep wrote: > Guy Marcenac wrote: >> Tom Eastep wrote: >>> Tom Eastep wrote: >>>> This ISN'T a Shorewall problem. Neither Shorewall nor Netfilter have any >>>> control over where the log messages go (or if they go) when the LOG >>>> target is used. >>> And if I had to guess, I would say that there is something wrong with >>> klogd. klogd is the daemon that monitors the kernel's ring buffer and >>> forwards the messages to syslogd. Your test with 'logger' uses the >>> 'syslog()' API which doesn't go through the ring buffer. >>> >> What I do not understand is that info messages from postfix, for >> instance, are normally logged >> > > Have you restarted klogd? It is KERNEL logging that isn't working so you > need to focus on that path. Testing with logger or noting that postfix > logging works simply validates that the problem is NOT WITH SYSLOGD. > I was completly focussed on syslogd and restarting klogd did the trick. Thank you Tom
-- Guy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
