[Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf

[Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf

[Joachim Wiberg]

Hi everyone!

I'm posting this as an RFC patch to see what you think about updating
the default syslog.conf for the sysklogd package to match upstream.

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.

Best regards
 /Joachim

Joachim Wiberg (1):
  package/sysklogd: update default syslog.conf to match upstream

 package/sysklogd/syslog.conf | 69 +++++++++++++++++++++++++++++++++---
 1 file changed, 64 insertions(+), 5 deletions(-)

-- 
2.25.1

[Buildroot] [RFC PATCH 1/1] package/sysklogd: update default syslog.conf to match upstream

[Joachim Wiberg]

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
---
 package/sysklogd/syslog.conf | 69 +++++++++++++++++++++++++++++++++---
 1 file changed, 64 insertions(+), 5 deletions(-)

diff --git a/package/sysklogd/syslog.conf b/package/sysklogd/syslog.conf
index 411bd645ff..8e4f9e2059 100644
--- a/package/sysklogd/syslog.conf
+++ b/package/sysklogd/syslog.conf
@@ -1,9 +1,68 @@
-# /etc/syslog.conf - Configuration file for syslogd
+# /etc/syslog.conf - Configuration file for syslogd(8)
+#
+# For information about the format of this file, see syslog.conf(5)
+#
 
-auth,authpriv.*		/var/log/auth.log
-*.*;auth,authpriv.none	/var/log/messages
-user.*			/var/log/user.log
+#
+# First some standard log files.  Log by facility.
+#
+auth,authpriv.*			 /var/log/auth.log
+*.*;auth,authpriv.none		-/var/log/syslog
 
-*.emerg			*
+#cron.*				/var/log/cron.log
+#daemon.*			-/var/log/daemon.log
+kern.*				-/var/log/kern.log
+#lpr.*				-/var/log/lpr.log
+mail.*				-/var/log/mail.log
+#user.*				-/var/log/user.log
 
+#
+# Logging for the mail system.  Split it up so that
+# it is easy to write scripts to parse these files.
+#
+#mail.info			-/var/log/mail.info
+#mail.warn			-/var/log/mail.warn
+mail.err			 /var/log/mail.err
+#mail.*;mail.!=info		-/var/log/mail
+#mail,news.=info 		-/var/log/info
+
+# The tcp wrapper loggs with mail.info, we display all
+# the connections on tty12
+#
+#mail.=info			/dev/tty12
+
+#
+# Some "catch-all" log files.
+#
+#*.=debug;\
+#	auth,authpriv.none;\
+#	news.none;mail.none	-/var/log/debug
+*.=info;*.=notice;*.=warn;\
+	auth,authpriv.none;\
+	cron,daemon.none;\
+	mail,news.none		-/var/log/messages
+
+# Store all critical eventes, except kernel logs in critical
+#
+#*.=crit;kern.none		/var/log/critical
+
+# Example of sending events to remote syslog server.
+# All events from notice and above, except auth, authpriv
+# and any kernel message are sent to server finlandia in
+# RFC5424 formatted output.
+#
+#*.notice;auth,authpriv.none;
+#	kern.none\		@finlandia	;RFC5424
+
+# Emergencies are sent to anyone logged in
+#
+*.=emerg			*
+
+# Priority alert and above are sent to the operator
+#
+#*.alert				root,joey
+
+#
+# Include all config files in /etc/syslog.d/
+#
 include /etc/syslog.d/*.conf
-- 
2.25.1

[Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf

[Thomas Petazzoni]

On Sat, 30 Jan 2021 14:52:02 +0100
Joachim Wiberg <troglobit@gmail.com> wrote:

> I'm posting this as an RFC patch to see what you think about updating
> the default syslog.conf for the sysklogd package to match upstream.
> 
> 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.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf

[Joachim Wiberg]

On Sun, Jan 31, 2021 at 23:13, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Sat, 30 Jan 2021 14:52:02 +0100 Joachim Wiberg <troglobit@gmail.com> 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

[Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf

[Thomas Petazzoni]

On Sun, 31 Jan 2021 23:58:26 +0100
Joachim Wiberg <troglobit@gmail.com> wrote:

> 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.

I don't have a strong opinion on what should be our default
configuration for sysklogd. Peter, do you have any comments ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > On Sun, 31 Jan 2021 23:58:26 +0100
 > Joachim Wiberg <troglobit@gmail.com> wrote:

 >> 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.

 > I don't have a strong opinion on what should be our default
 > configuration for sysklogd. Peter, do you have any comments ?

Not really. People can still use a custom configuration file in their
rootfs overlay, so I don't have a problem with changing the default
configuration to be more "normal", E.G. what upstream suggests.

-- 
Bye, Peter Korsgaard

[Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf

[Joachim Wiberg]

On Mon, Feb 01, 2021 at 10:43, Peter Korsgaard <peter@korsgaard.com> wrote:
> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
>  > On Sun, 31 Jan 2021 23:58:26 +0100
>  > Joachim Wiberg <troglobit@gmail.com> wrote:
>  >> 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.
>  > I don't have a strong opinion on what should be our default
>  > configuration for sysklogd. Peter, do you have any comments ?
> Not really. People can still use a custom configuration file in their
> rootfs overlay, so I don't have a problem with changing the default
> configuration to be more "normal", E.G. what upstream suggests.

All right, thank you so much to both of you for your time!

I'll prepare a patch to drop the local syslog.conf and use the one
shipped with sysklod.


Best regards
 /Joachim