Red Hat Bugzilla – Bug 83625
'dmesg -n $LOGLEVEL' get overwriten by syslog service
Last modified: 2014-03-16 22:34:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a)
Description of problem:
The setup of the console message level is overwirten by the syslog service.
The initial setup of the console si done in:
with the command:
# Fix console loglevel
/bin/dmesg -n $LOGLEVEL
but, later with the syslog is started, the configuration done in /etc/rc.sysinit
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure syslog to start at boot time
2. reboot your system
3. run cat /proc/sys/kernel/printk
Actual Results: cat /proc/sys/kernel/printk
6 4 1 7
Expected Results: cat /proc/sys/kernel/printk
3 4 1 7
The number 3 is configured in the variable:
in the file:
Maybe the console dmesh initialization can be run from rc.local
or at the end of /etc/init.d/syslog
Found a nice solution:
Set this variable:
KLOGD_OPTIONS="-x -c 3"
in this file:
The key part is to add "-c 3" to the variable KLOGD_OPTIONS
This solution makes variable LOGLEVEL in:
obsolete only when the service syslog is used.
The default /etc/sysconfig/init says that syslogd will reset the console
loglevel; hence, this isn't really a bug.
I think the bug is only described in:
The issue is not solved in /etc/sysconfig/init, thats why I opened the bug.
Because initscripts fails to set the console loglevel.
It is a bug or at least a feature that does not work.
Please let me know if there will be a solucion for setting the console level in
all cases. (when syslog is used)