summaryrefslogtreecommitdiffstats
path: root/plugins/imtcp/imtcp.c
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2011-03-18 14:21:09 +0100
committerRainer Gerhards <rgerhards@adiscon.com>2011-03-18 14:21:09 +0100
commitbb67fd7fbf99ce0ec01b347fad5d1d9d101bfa5d (patch)
treeec467b96d9b511d887e945bc938b6e7522189104 /plugins/imtcp/imtcp.c
parentf057fb2db388cc16475f9c5a7de64aeb1f3bdb43 (diff)
downloadrsyslog-bb67fd7fbf99ce0ec01b347fad5d1d9d101bfa5d.tar.gz
rsyslog-bb67fd7fbf99ce0ec01b347fad5d1d9d101bfa5d.tar.bz2
rsyslog-bb67fd7fbf99ce0ec01b347fad5d1d9d101bfa5d.zip
experimental: support for systemd-induced second PRI in klog
if systemd writes a kernel log entry with a non-kernel priority, the priority recorded in the kernel log will be wrong. However, it will be immediately followed by another priority (with the kernel timestamp in between, if enabled). So imklog now tries to see if there is a second PRI and, if so, uses it. Note that we already support non-kernel PRIs in the kernel log, as this was done in BSD for quite some while. HOWEVER the config statement "$klogpermitnonkernelfacility on" must be used to permit this (otherwise non kernel messages are dropped). Sample of a such a message on a kernel without timestamping enabled: $ echo '<14>text' > /dev/kmsg $ dmesg -r <4><14>text NOTE: support for timestamp is NOT YET ENABLED!
Diffstat (limited to 'plugins/imtcp/imtcp.c')
0 files changed, 0 insertions, 0 deletions