Re: [PATCH 1/3] dmesg: handle multi-char log levels

On Tuesday 18 December 2012 14:49:18 Peter Korsgaard wrote: Since Linux 3.5 (7ff9554bb5: printk: convert byte-buffer to variable-length record buffer), klog buffer can now contain log lines with multi-char loglevel indicators ([0-9]+) - So we can no longer just skip 3 bytes. Instead skip up

Re: [PATCH 3/3] syslogd: add option to log to Linux kernel printk buffer

On Tuesday 18 December 2012 14:49:20 Peter Korsgaard wrote: + /* + kernel 3.5 expects single char printk KERN_* priority prefix, + from 3.5 onwards the full syslog facility/priority format is supported + */ comment style is slightly off. needs '*' at the start of each

Re: [PATCH 1/3] dmesg: handle multi-char log levels

Mike == Mike Frysinger vap...@gentoo.org writes: Hi, Mike doesn't seem to work Mike allnoconfig + dmesg + dmesg pretty enabled Mike $ ./busybox dmesg Peer 86.165.245.161:29833/59757 unexpectedly shrunk window 2138950115:2138952928 (repaired) Peer 86.165.245.161:29833/59757

Re: [PATCH 3/3] syslogd: add option to log to Linux kernel printk buffer

Mike == Mike Frysinger vap...@gentoo.org writes: Mike On Tuesday 18 December 2012 14:49:20 Peter Korsgaard wrote: + /* + kernel 3.5 expects single char printk KERN_* priority prefix, + from 3.5 onwards the full syslog facility/priority format is supported + */ Mike

[PATCH 2/3] klogd: handle multi-char log levels

Since Linux 3.5 (7ff9554bb5: printk: convert byte-buffer to variable-length record buffer), klog buffer can now contain log lines with multi-char loglevel indicators ([0-9]+) - So use strtoul to parse it. function old new delta klogd_main

[PATCH 1/3] dmesg: handle multi-char log levels

Since Linux 3.5 (7ff9554bb5: printk: convert byte-buffer to variable-length record buffer), klog buffer can now contain log lines with multi-char loglevel indicators ([0-9]+) - So we can no longer just skip 3 bytes. Instead skip past the terminating '' like util-linux does. function

[PATCH 3/3] syslogd: add option to log to Linux kernel printk buffer

Why invent our own shared memory circular buffer when the kernel has a perfectly fine one already? This can be used as a smaller/simpler alternative to the syslogd IPC support (as IPC shmem/klogd/logread aren't needed), while also allowing centralised logging of everything (kernel messages,

v2: Kernel printk buffer handling updates

Hi, Linux 3.5 extended the /dev/kmsg interface for injecting log messages from user space into the kernel printk buffer to accept (and store) the full syslog facility/priority value. The following patch series updates dmesg and klogd to handle this, and adds an alternative to the syslogd ipc

Re: [PATCH 3/3] syslogd: add option to log to Linux kernel printk buffer

On Saturday 05 January 2013 18:07:19 Peter Korsgaard wrote: +#else +void kmsg_init(void); +void kmsg_cleanup(void); +void log_to_kmsg(int pri, const char *msg); +#endif /* FEATURE_KMSG_SYSLOG */ ... + if (ENABLE_FEATURE_KMSG_SYSLOG (option_mask32 OPT_kmsg)) { +

Re: [PATCH 1/3] dmesg: handle multi-char log levels

On Saturday 05 January 2013 18:07:17 Peter Korsgaard wrote: Since Linux 3.5 (7ff9554bb5: printk: convert byte-buffer to variable-length record buffer), klog buffer can now contain log lines with multi-char loglevel indicators ([0-9]+) - So we can no longer just skip 3 bytes. Instead skip

Re: [PATCH 2/3] klogd: handle multi-char log levels

On Saturday 05 January 2013 18:07:18 Peter Korsgaard wrote: Since Linux 3.5 (7ff9554bb5: printk: convert byte-buffer to variable-length record buffer), klog buffer can now contain log lines with multi-char loglevel indicators ([0-9]+) - So use strtoul to parse it. pushed -mike signature.asc

Re: [PATCH] sha3sum: New applet, v2

Hi Lauri, On Fri, Jan 04, 2013 at 01:02:53PM +0200, Lauri Kasanen wrote: From 84768213e7a004b9e703a1d7091bd43b34822e0c Mon Sep 17 00:00:00 2001 From: Lauri Kasanen cur...@operamail.com Date: Thu, 3 Jan 2013 21:10:01 +0200 Subject: [PATCH] sha3sum: New applet, v2 - Sorted the enum by alpha