Le mardi 07 février 2012 à 16:22 +0100, Peter Czanik a écrit :

Hello, Last week and today I experimented with journal on openSUSE Factory and Fedora Rawhide. For all details, please check my blogs:

http://czanik.blogs.balabit.com/2012/02/journal-and-syslog-ng/ and

https://czanik.blogs.balabit.com/2012/02/journal-and-syslog-ng-revisited-on-...

As I don't know, which is a bug or a feature, here is a list of openSUSE related problems, let me know which to report in bugzilla:

- output from "logger bla" (and most of the syslog messages) does not show up in the journal (output of systemd-journalctl), only in /var/log/messages (on Rawhide all logs are stored in the journal and forwarded to syslog).

it might be related to https://bugzilla.novell.com/show_bug.cgi?id=728565 (rsyslog is still using /etc/rsyslog.early.conf, even after early boot)

- when replacing rsyslog with syslog-ng (zypper rm rsyslog), rsyslog keeps running. syslog-ng can't be started with "systemctl restart syslog.service". It turned out, that one also needs a "*systemctl deamon-reload". Could this be added to post install, or that would have additional side effects?

- "rcsyslog stop" / "systemctl stop syslog.service" does not work, syslog-ng starts immediately again (also affects rsyslog).

- after a "kill -9" on syslog-ng, "systemctl status syslog.service" shows syslog-ng active/running and exited/killed at the same time :-) It can't be started again by "systemctl start syslog.service"

I must confess the way *syslog* is a bit too tricky to me, better to ask Werner about it ;)

- I don't know, if /dev/log vs. /run/systemd/journal/syslog should be addressed in syslog-ng.conf

No opinion, and Fedora hasn't done the support for it yet. -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org