Tom Eastep wrote: > Chuck Kollars wrote: >> The pre-defined >> levels (in decreasing order) are: >> >> emerg – system is or will be unusable if situation >> is not resolved >> alert – immediate action required >> crit – critical situations >> warning – recoverable errors >> notice – unusual situation that merits >> investigation; a significant event that is typically >> part of normal day-to-day operation >> info – informational messages >> debug – verbose data for debugging >> >> You control this with configuration of "syslog" itself >> (often via the file /etc/syslog.conf). You control >> which messages go into which file(s) and/or onto which >> screen(s). > >> Specifying a level normally >> gives you that level _and_all_levels_above_it_, so for >> example if you specify level "crit" you'll also get >> levels "alert" and "emerg". > > Note that the above list is in decreasing order of message importance. > It follows that those messages with levels at the top of the list are > more important than those with levels at the bottom. Hence, giving a > message a level toward the bottom of the list is likely to suppress its > being written to some (sometimes all) of the logs.
BTW: I was addressing my remarks to John, not to Chuck. Hope that was clear... -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
