3 ms·
Syslog has been a thing long before systemd decided they needed their own solution. The problem that you're describing that they solved is the fact that other
by elmerfud 5y ago
Syslog has been a thing long before systemd decided they needed their own solution. The problem that you're describing that they solved is the fact that other applications also seem to like to reinvent everything instead of just using what's there.
- ok123456 5y agoIf your application uses syslog... 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.
- elmerfud 5y agoI think you're confirming everything that I just said. There's an existing robust logging solution that has been around for a long time and is very mature. Yet people's continue to do the let's build a new thing to solve the same problem because I can't be bothered to use the existing solution.