“Are you an old-school Linux sysadmin who dislikes or doesn't want systemd?
twitter.com
twitter.com
Why does systemd need it's own logging magic? I guess logging was never done prior to systemd. They literally had one corner case to solve for which means they decided to reinvent logging around instead of just solving for that one issue in already mature solutions.
Why does it need to own time sync... Because I guess they feel that can do it in a more complete, more secure, and less buggy way than the existing mature products.
I could go on and on about this nonsense that has been shoved down the users throat by the enterprise Linux giants. The sad thing is, there now seems to be a whole crop of users who don't remember the core philosophy of do one thing and do it very very well. So there's been an explosion of other things that try and suck in everything and duplicate efforts. They all seem to do their core problem well but all the ancillary things that they reinvent along the way they totally suck at.
Bringing up freeBSD. I'll deal with the irritating pain of systemd and the Enterprise Linux overlords then deal with the whole host of problems that come with FreeBSD
If you want deal with configuring syslogd so it just doesn't get all dumped to the same log file as everything else in your system...
"Just use syslog" is really a non-answer. The systemd journal stuff goes above and beyond that and provides sane defaults, and it's universal.