grsecurity forums

Hi all,
I'm using grsecurity after quite a long time (hem... I had a 2.4.26... so can imagine how long it is!).
I remember that any "deny" was logged via syslogd so that I could easily fix any ACL in few minutes. Now I'm using 2.4.33rc2 with latest grsec patch, but I cannot find the way to enable syslogging anymore: messages go only to console, but it's some KMs far from my workplace... so you can imagine that it not easy to debug/solve the situation!
Is there a new way to enable loggin of all grsec action? I read in latest changelog that it "should be" a sysctl-tunable action now... is it right? I cannot find nothing about it in official documentation.

Any help will be apreciated!
Thanks

Have you changed your syslog config? Does it log any other kernel messages?

Your hint about the kernel messages has been providential: I found that the syslogd script in init.d directory did _not_ start klogd. To solve the problem I simply had to start klogd.

Sorry for the stupid question.