[wpkg-users] [Bug 98] Logging Inacuracy
bugzilla-daemon at bugzilla.wpkg.org
bugzilla-daemon at bugzilla.wpkg.org
Sat Feb 16 12:21:34 CET 2008
http://bugzilla.wpkg.org/show_bug.cgi?id=98
Rainer Meier <skybeam at users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |skybeam at users.sourceforge.ne
| |t
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Rainer Meier <skybeam at users.sourceforge.net> 2008-02-16 12:21:30 ---
Well, I think this this is a user error. Let me explain you why.
The log level is defined as a bitmask:
Bit Dec Description
1 1 log errors only
2 2 log warnings
3 4 log information
4 8 log audit success
5 16 log audit failure
What you specified is a bitmask in HEX notation.
0x13 = 19d = 10011
=> logs errors, warnings and audit failures
0x12 = 18d = 10010
=> logs warnings and audit failures
0x15 = 21d = 10101
=> logs errors, information and audit failure
0x4 = 4d = 00100
=> logs information only
If you need assistance converting hex to decimal or binary just fire up the
Windows calculator: Start => Run... => calc
Then go to View and select Scientific format.
Now you can select the Hex radio button and enter hex numbers. Or switch to Bin
and enter the desired binary mask. When you leave the number in calc and switch
to another number format (Hex/Dec/Bin) the current number will be converted.
So I am closing this bug report as I think it is clearly a user error. Please
re-open in case it isn't.
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the wpkg-users
mailing list