Hello, On Mon, Dec 02, 2024 at 01:08:52PM +0100, Nicolas George wrote: > We do not want a different logging system for each daemon.
Unfortunately rather common practice though even before systemd-journald of course: Exim, Apache HTTPD Server, HAProxy, … (some of these CAN be configured to log to syslog, it's just not their default state) I think in the past syslog was regarded as fairly low throughput and potentially slow to complete. Also older syslog implementations could only filter by facility and priority. So high throughput logging like for a web server (access logs etc), which also often wanted to split by things like vhost, were encouraged to do own logging. Decent syslog implementations like rsyslog or syslog-ng have been fast and full of features for ages though. Maybe app authors don't want to assume their presence - and assume which one? App-specific logging does have the benefit that the documentation for splitting the logs by some attribute can come with the app. I am in two minds whether the prevalence of journald will encourage or discourage projects from growing their own logs. On the one hand it's easy to display by unit, on the other hand I rarely see people doing that and when there's a lot of logs they just complain. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
