Em 16-10-2015 02:37, Pierre Labastie escreveu:
> Hi,
>
> Just want to share something everybody may be knowing already...
>
> In the past years, we have seen more and more kernel messages cluttering
> the screen (when mounting an ext2 system, when setting up network, etc).
> It culminates with the LVM tests, where it is almost impossible to work
> on another console during the tests (since the kernel messages go the
> the console you are working on, not the console where you started the
> test).
>
> The command "dmesg -D" can be used to avoid those annoyances. Normally,
> critical messages should still show up through the sysklogd system.
>
> Pierre
>
It is good discussing this. First time I wrote to help a client, IIRC,
DJ warned me, because I instructed a user to change a bootscript. :-)
Found in man 2 syslog.
Kernel constant Level value Meaning
KERN_EMERG 0 System is unusable
KERN_ALERT 1 Action must be taken immediately
KERN_CRIT 2 Critical conditions
KERN_ERR 3 Error conditions
KERN_WARNING 4 Warning conditions
KERN_NOTICE 5 Normal but significant condition
KERN_INFO 6 Informational
KERN_DEBUG 7 Debug-level messages
I use /etc/sysconfig/rc.site:
$ grep LOGLEVEL /etc/sysconfig/rc.site
#LOGLEVEL=5
LOGLEVEL=3
Perhaps it would do with level 4.
--
[]s,
Fernando, aka SÃsifo
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
