On Thu, Jul 14, 2011 at 13:52, Karel Zak <kzak@xxxxxxxxxx> wrote: > I did some changes to dmesg(1) in last days: > > * \x<hex> encoding is used for non-printable chars and invalid > multibyte sequences > > * add --decode option to decode facility and level (priotity) number to > human readable prefixes, for example: > > $ dmesg --decode > kern :info : [53335.593617] ata1.00: configured for UDMA/100 > kern :info : [53335.743185] PM: resume of devices complete after 2496.795 msecs > kern :debug : [53335.743593] PM: Finishing wakeup. > kern :warn : [53335.743595] Restarting tasks ... done. > kern :info : [53335.790452] video LNXVIDEO:00: Restoring backlight state > > * add --facility=<LIST> option to filter out messages, for example: > > $ dmesg --facility=daemon,user > [ 1.802065] dracut: dracut-009-11.fc15 > [ 1.811267] dracut: rd.luks=0: removing cryptoluks activation > [ 1.813913] dracut: rd.lvm=0: removing LVM activation > [ 1.819348] udev[111]: starting version 167 > > * add --level=<LIST> option to filter out messages, for example: > > $ dmesg --level=debug,info > > $ dmesg --facility=kern --level=warn,err > > * add --clear option to clear the kernel ring buffer > > * add --read-clear to read and clear the kernel ring buffer > > * add --console-off and --console-on to control output to console > > * -n <LEVEL> (--console-level) supports human readable level names, > for example: > > $ dmesg --console-level=emerg,alert > > Comments & suggestions? Sounds all great. Thanks for adding this before people start complaining that we fill the kernel log with 'userspace crap'. I actually removed all syslog daemons from my systems, and use only 'dmesg' these days, and no log is stored on disk, I just don't need it. People ask since a while for an option to suppress the kernel's [...] timestamp from the 'dmesg' output. Maybe you can make them happy too. :) Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html