Hi, On Wed, 17 Apr 2013, Cristian Rodríguez wrote:
And voila: last message in syslog is
Apr 17 14:28:55 susi dhclient[1923]: DHCPREQUEST on air to ...
Apr 17 14:31:07 susi.home.s3e.de systemd-journal[249]: Forwarding to syslog missed 1 messages. Everything after that is missing from syslog.
What do you mean ? You are not expressing your problem correctly I am afraid
Isn't that obvious? After the DHCPREQUEST entry there should be more entries following. There aren't, so they are missing. Stefan complains about that. Correctly so.
=> journald does not work as advertised.
WHAT? it does work as expected,
huh? It surely isn't expected to stop forwarding messages to syslog once there was an error in transmission (which is also highly unlikely to occur, certainly syslog buffers aren't full because of one DHCP syslog entry).
unless your expectatives are different or distorted..
If you could stop being obnoxious I would be thankful.
Can I prevent systemd/journald's occupation of the syslog socket somehow?
No, This is a mandatory feature.
Then it better be fixed, right? Ciao, Michael.