Bug 3793 - Changing the log output level value makes no difference
Summary: Changing the log output level value makes no difference
Status: RESOLVED WORKSFORME
Alias: None
Product: Busybox
Classification: Unclassified
Component: Standard Compliance (show other bugs)
Version: 1.18.x
Hardware: Other Linux
: P3 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 21:43 UTC by Dan
Modified: 2011-09-11 17:37 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dan 2011-05-25 21:43:56 UTC 
Changing the log output level value to anything between 0-7 makes no difference from the debug value 7 in syslog.
Comment 1 Denys Vlasenko 2011-05-29 00:21:05 UTC 
Tested "syslogd -l 5":

Message generated by "logger -p 5 TEST" is not logged.
Message generated by "logger -p 4 TEST" is logged.

Seems to work.

If it doesn't work for you, describe your exact situation.
Comment 2 Dan 2011-05-31 00:57:31 UTC 
I am using OpenWrt (on a Netgear WNDR3700).
It uses BusyBox sysklogd unmodified, programs logging there use either the "logger" utility or the "openlog()" and "syslog()" api calls, so nothing OpenWrt specific.
If I set the log output level to anything between 0-7, then try it one by one, the log looks like this in each case:

May 31 02:14:16 BLACKPORT user.debug root: TEST MSG
May 31 02:14:19 BLACKPORT user.info root: TEST MSG
May 31 02:14:22 BLACKPORT user.notice root: TEST MSG
May 31 02:14:25 BLACKPORT user.warn root: TEST MSG
May 31 02:14:28 BLACKPORT user.err root: TEST MSG
May 31 02:14:31 BLACKPORT user.crit root: TEST MSG
May 31 02:14:34 BLACKPORT user.alert root: TEST MSG
May 31 02:14:37 BLACKPORT user.emerg root: TEST MSG
Comment 3 Denys Vlasenko 2011-06-01 21:41:25 UTC 
(In reply to comment #2)
> I am using OpenWrt (on a Netgear WNDR3700).
> It uses BusyBox sysklogd unmodified,

What is its version?

> programs logging there use either the
> "logger" utility or the "openlog()" and "syslog()" api calls, so nothing
> OpenWrt specific.
> If I set the log output level to anything between 0-7,

How exactly do you set it?

> then try it one by one,

...by running which command?

> the log looks like this in each case:
> 
> May 31 02:14:16 BLACKPORT user.debug root: TEST MSG
> May 31 02:14:19 BLACKPORT user.info root: TEST MSG
> May 31 02:14:22 BLACKPORT user.notice root: TEST MSG
> May 31 02:14:25 BLACKPORT user.warn root: TEST MSG
> May 31 02:14:28 BLACKPORT user.err root: TEST MSG
> May 31 02:14:31 BLACKPORT user.crit root: TEST MSG
> May 31 02:14:34 BLACKPORT user.alert root: TEST MSG
> May 31 02:14:37 BLACKPORT user.emerg root: TEST MSG
Comment 4 Denys Vlasenko 2011-09-11 17:37:13 UTC 
Works for me...