Re: Where do `pr_warning()`s end up?

[Alois Mahdal <alois.mahdal.1-ndmail@zxcvb.cz>]

On Sat, 9 Feb 2013 13:19:31 +1300
Chris Bannister <cbannister@slingshot.co.nz> wrote:
> [...]
> 
> Start looking here:
> 
> root@tal:~# less /etc/sysctl.conf
> [...]
> 
> # Uncomment the following to stop low-level messages on console
> #kernel.printk = 3 4 1 3
> [...]

Looks interesting, although from what I understood from reading kernel
sources (but maybe I'm being lost), pr_warning() is a macro around
eprintf() which is wrapper around vfprintf(), which is standard C
function (stdio.h, `man vfprintf`).

I.e. these calls do not use printk().

Will try altering these, though...


> Dang, if I can remember where the info is about the kernel "noise"
> levels.

Found it in kernel source, ./Documentation/sysctl/kernel.txt:

    printk:

    The four values in printk denote: console_loglevel,
    default_message_loglevel, minimum_console_loglevel and
    default_console_loglevel respectively.

    These values influence printk() behavior when printing or
    logging error messages. See 'man 2 syslog' for more info on
    the different loglevels.

    - console_loglevel: messages with a higher priority than
      this will be printed to the console
    - default_message_loglevel: messages without an explicit priority
      will be printed with this priority
    - minimum_console_loglevel: minimum (highest) value to which
      console_loglevel can be set
    - default_console_loglevel: default value for console_logleve


Too bad that I won't be able to reproduce the original issue which was
specific to password-protected SD cards.  Since I don't have that card
now.

Or I'll just try to play with the values anyway: what bad can happen to
me? ;-D


Thanks for pointer.

aL.

-- 
Alois Mahdal