[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/6 v2] logging refactoring

On 12/15/2009 05:47 PM, Pete Zaitcev wrote:
On Tue, 15 Dec 2009 17:38:18 -0500
Jeff Garzik<jeff@xxxxxxxxxx>  wrote:

In fact, does anyone even understand why we continue to split
LOG_WARNING and LOG_ERR? We really have three log levels:
   - debug
   - info (which is actually an error)
   - error (not really all that different from info actually)
Might as well create HAIL_DEBUG, HAIL_INFO, and HAIL_ERR (to be
used before exit(1), with values of 0,1,2 and remap to syslog
values where it goes to syslog.

It would be nice to disconnect from syslog, yes.  But the 'warning' log
level has value.

Can you offer any guidelines that are easy to follow and enforce?
I am often confused and select the level randomly. The only rule
I follow is: if and only if it's under if (debugging), then LOG_DEBUG.
Otherwise... hmm...

Sure, man 3 syslog :)

Err - error message, that will probably kill the server.
Warn - warning message - bad, but not fatal to the server
info - information message, like startup messages
debug - debugging messages, of interest mainly to programmers


To unsubscribe from this list: send the line "unsubscribe hail-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [XFree86]

Add to Google Powered by Linux