26 Aug
2011
26 Aug
'11
09:48
Hello, On 08/25/2011 10:34 AM, Peter Czanik wrote: > On 08/25/2011 09:45 AM, Peter Czanik wrote: >> And here are my logs. Lines, where the message starts with 'bla' are >> sent with logger in the following form: logger bla `date` When using >> tail -f on logs, it seemed to me, that logs are received only when a >> kernel message (like the one from firewall on ssh login) arrives. It >> only seems to be a problem with systemd. I'll check it with Fedora >> alpha, as that also has systemd and syslog-ng 3.2.4. Or just wait a few >> days, as syslog-ng 3.3 should arrive to factory in any minute... > Just tested, rsyslog seems to work correctly with systemd. And our git > tree ( http://git.balabit.hu/?p=bazsi/syslog-ng-3.2.git;a=summary ) has > some systemd related patches, which were committed after the syslog-ng > 3.2.4 release. As syslog-ng 3.3 sources are already in factory and have > these patches, I'll come back to this question once the 3.3 binary is > available. OK, it arrived to factory this morning, so I could test it. Logging with syslog-ng works now as epxected. I still ran into a couple of systemd related issues, which I still need to test a bit more before reporting to bugzilla: - changing from rsyslog to syslog-ng or back seems to work only after a reboot - when editing syslog-ng.conf and making a mistake, the error message is not printed on screen on "rcsyslog restart" making it difficult to find the problem or even to find that there is a problem... Neither of these problems appear with good old-fashioned sysvinit... Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org