RFC package/sysklogd: proposal to update default syslog.conf
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 1 patch 0 repliesNew
Patches in v1 No applies recorded yet
The patch the cover letter announces is not in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf
Quoted 9 lines · Thomas Petazzoni
Quoted 4 lines · On Sat, 30 Jan 2021 14:52:02 +0100 Joachim Wiberg <[email protected]> wrote:
The updated file changes the default log file from messages to syslog, as is common on most modern systems today. The messages remains but only for less critical messages. The update also adds more examples for how to enable remote logging as well as different new log formats.
Well, if the syslog.conf that we have in package/sysklogd/ is exactly the one contained in the sysklogd sources, then what is the point of having a copy in package/sysklogd/ ? We could just as well install the configuration file provided by upstream.
True, no point in having a local copy.
My main question was if there was any specific reason to sticking with the old habits of only using /var/log/messages, as BusyBox syslogd does, or if every logging package is free to have its own defalts? Within reason, of course. I'm just a bit concerned with breaking peoples defaults, even though they can just provide their own.
If it's OK to change for sysklogd, I can post a new patch that drops the locallay maintained .conf and instead installs the sysklogd one.
Best regards
/Joachim