![](https://seccdn.libravatar.org/avatar/0edf09abc2dffb4df54af190ea29ffa1.jpg?s=120&d=mm&r=g)
On 08/19/2011 02:11 PM, Stefan Seyfried wrote:
Hi all,
this issue is so strange, that I'd first like to ask if someone else is also seeing this before filing a bug report :-)
System: * pretty current FACTORY * running systemd * running rsyslogd
Symptoms: * "logger foo" does nothing. No entry in /var/log/messages or anywhere * "strace logger foo" does work. * "echo foo > /dev/kmsg" also works as a workaround.
anyone else seeing this? I did not try strace, but gave a quick test to syslog-ng (as I'm from syslog-ng upstream...). It's only slightly better: the first "logger bla" seems to come through, but no more additional logs until restart.
In another thread, when I asked about systemd and syslog-ng packaging, I got this answer: "Werner is working on a systemd-generator which should take care of systemd .service generation at startup for syslog-ng. I'd say, don't worry for systemd right now." So I suppose, that if you need logging, you should change back to sysvinit for now... Bye, -- Peter Czanik (CzP) <czanik@balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org