Comment Re:They will care, probably sooner than they think (Score 1, Insightful) 128
Even this is something journald does so much better than syslog
You are cherry-picking the one thing that isn't logged by most syslog daemons by default,, in a disingenious attempt to show that syslog is "worse", even though it is off by default because it is of little use. If we cared AT ALL to have the "log level" information, it would be logged.
The discussions of the many limitations of syslog,
Fine. Then solve the problem where it should be solved, and add this to
# probably already in the config
source src { system(); internal(); }# here's your damn filter
filter f_err_only { level( "error"}; };# pre-filtered log output
destination err_only_log { file("/var/log/err_only_messages"); };# link the filter to a destination
log { source(src); filter(f_err_only); destination(err_only_log); };
Now you can read those messages only using "less". You DID know that syslog has very flexible log routing and filtering capabilities, right?
claiming that regular expressions are easy is laughable.
If regex is too hard, you might as well give up now. Regex is only hard if you abuse it badly, which is true for any programming language. This is just trolling at this point.
Oh, and thanks for admitting you are an inexperience n00b. You may have been using linux since the early slackware days, but didn't seem to learn much.
As for your "challenge", I have yet to see any systemd apparatchik rise to the challenge to prove that systemd isn't an unmaintainable monolithic mess, by showing how to replace (NOT CHAIN) journald with syslog-ng or indeed run any of the systemd components in isolation.