El 17/04/13 11:51, Cristian Rodríguez escribió:
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..
Messages told to be "missed" are stored in the journal (in the past, when syslog was the only way, those messages were simply lost) in this context "missed" means that the syslog socket buffer is full and can't take it anymore. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org