Hi, I've noticed that linux kernels before this commit behave differently in rsyslog: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=7ff9554bb578ba02166071d2d487b7fc7d860d62
What I've observed is if I do something like the following in kernels before this patch: # echo test > /dev/kmsg This will show up in kern.log with something as simple as: kern.* /var/log/kern.log However kernels after that patch no longer show up in kern.log with the same rule. What I've noticed is the default userspace kmsg priority level is different (observed via dmesg -r): Before that patch if we echo something into /dev/kmsg we get: <4>[ 35.084348] before If we do it on or after that patch we get: <12>[ 71.091005] after According to this documentation: http://www.mjmwired.net/kernel/Documentation/ABI/testing/dev-kmsg The <N> value is both the priority and facility combined (after that patch was introduced). Is there a way to specify kernel priority/facility levels greater than 7 in order to log userspace generated kmsg entries? Thanks, --chris j arges _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
