All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: util-linux@vger.kernel.org
Cc: Lennart Poettering <lennart@poettering.net>
Subject: dmesg(1) changes
Date: Thu, 14 Jul 2011 13:52:31 +0200	[thread overview]
Message-ID: <20110714115231.GF3486@nb.net.home> (raw)


 Hi,

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?

    Karel
-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

             reply	other threads:[~2011-07-14 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 11:52 Karel Zak [this message]
2011-07-14 12:40 ` dmesg(1) changes Lennart Poettering
2011-07-18  9:52   ` Karel Zak
2011-07-14 13:45 ` Kay Sievers
2011-07-18 13:00 ` Thomas Bächler
2011-07-18 22:28   ` Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110714115231.GF3486@nb.net.home \
    --to=kzak@redhat.com \
    --cc=lennart@poettering.net \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.