4 ms·
From the log producing side, journald is much better than log files. No one wants to manually configure log rotation for each daemon individually (What signal d
by nolist_policy 3y ago
From the log producing side, journald is much better than log files. No one wants to manually configure log rotation for each daemon individually (What signal does this daemon use to reopen its log file shudder). With systemd you just log to stdout+stderr and are done.
- throw0101b 3y ago> No one wants to manually configure log rotation for each daemon individually (What signal does this daemon use to reopen its log file shudder). I do. I want my (e.g.) auth.log rotated regularly and kept forever. Many other things I only care about (say) 4-6 weeks of retention. (This is in addition to off-host log shipping, which of course journald doesn't do itself so I have to run rsyslog regardlesss.)
- everforward 3y agoI would totally agree with this. I'm often both the producer and consumer though, and the consumer side is painful enough I tend to avoid journald. From the producer side, I typically use a logging library/extension that handles its own log rotation and doesn't require logrotate. It's a half-dozen lines of code or so, not too onerous.