[systemd-devel] systemd-logger and external syslog daemon
lennart at poettering.net
Fri Mar 11 08:17:17 PST 2011
On Fri, 11.03.11 09:55, Rainer Gerhards (rgerhards at hq.adiscon.com) wrote:
> > Sounds quite reasonable :)
> > What would be also really nice - some systemd specific marker so
> > rsyslog could extract syslogd messages from kmsg. Not sure if it is
> > really doable without some gross kernel hack though.
> > Special severity level may be ... PRINTK_SYSTEMD? :)
> There is also a subtle issue with the current systemd implementation, and
> that could potentially solved by such a setting.
> Systemd shuffles the system log socket to the kernel log. That is nice,
> because we have logging available right from the system start. However, in
> rsyslog users can configure different rules based on the log source. The
> issue now is that what used to be the local log socket source now becomes the
> kernel log source. I don't think this causes many problems in almost all
> environments, and I guess it would require some non-trivial "magic" in
> rsyslog to handle the situation (and I am not sure it is worth that). But I
> wanted to mention this point ;)
I think rules like this should look for the facility field, and we
should allow facility bits in the kmsg messages, so that userspace
messages can clearly mark themselves as such.
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel