Bug 83625 - 'dmesg -n $LOGLEVEL' get overwriten by syslog service
'dmesg -n $LOGLEVEL' get overwriten by syslog service
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-02-06 09:04 EST by Oliver Schulze L.
Modified: 2014-03-16 22:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-06 10:58:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Oliver Schulze L. 2003-02-06 09:04:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a)
Gecko/20021207 Phoenix/0.5

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
is lost.

Version-Release number of selected component (if applicable):

How reproducible:

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
should returns
3       4       1       7

The number 3 is configured in the variable:
in the file:

Additional info:

Maybe the console dmesh initialization can be run from rc.local
or at the end of /etc/init.d/syslog
Comment 1 Oliver Schulze L. 2003-02-06 09:28:01 EST
Found a nice solution:
Set this variable:
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.
Comment 2 Bill Nottingham 2003-02-06 10:58:24 EST
The default /etc/sysconfig/init says that syslogd will reset the console
loglevel; hence, this isn't really a bug.
Comment 3 Oliver Schulze L. 2003-02-06 11:02:23 EST
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)

Note You need to log in before you can comment on or make changes to this bug.