On 04/17/2013 05:28 AM, Stefan Seyfried wrote:
susi:~ # journalctl -b | grep Forwarding Apr 17 08:46:05 susi.home.s3e.de systemd-journal[249]: Forwarding to syslog missed 112 messages. Apr 17 08:46:46 susi.home.s3e.de systemd-journal[249]: Forwarding to syslog missed 31 messages.
This is correct, it is operating exactly as intended.
So it looks like syslog-ng is only started after the first "Forwarding to syslog missed..." message.
Yes, nothing wrong with that, what do you expect ? no messages "lost", as the log says the journal forwarded messages to syslog when it started, syslog is a regular service, it has to start waay *after* systemd begins logging..
I understand correctly: there is no way to get rid of journal completely and just log to syslog like we always did (or passing the messages from syslog to journal instead of the other, non-working way round)? Would it be possible to let the journal only handle systemd but keep away from the tradiditonal syslog socket?
No, and there is nothing wrong in what it is currently doing, care to explain exactly what you see it is wrong now ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org