[evla-sw-discuss] Terminology

[James Robnett]

  Is there a reason not to use the priority philosophy inherent in
syslog ?   It pretty much covers the options and has the added bonus
that (at a later date) you can use the syslog functionality if you want
to ....

   From 'man 2 syslog'

       #define KERN_EMERG    "<0>"  /* system is unusable               */
       #define KERN_ALERT    "<1>"  /* action must be taken immediately */
       #define KERN_CRIT     "<2>"  /* critical conditions              */
       #define KERN_ERR      "<3>"  /* error conditions                 */
       #define KERN_WARNING  "<4>"  /* warning conditions               */
       #define KERN_NOTICE   "<5>"  /* normal but significant condition */
       #define KERN_INFO     "<6>"  /* informational                    */
       #define KERN_DEBUG    "<7>"  /* debug-level messages             */

James

On Monday 27 October 2003 03:01 pm, Boyd Waters wrote:
> "information" - requires no action
> "warning"     - potential down-stream problems, but proceeding
> "failure"     - problems, can't continue
>
> "warning" and "failure", as listed above, seem both to be "errors":
>
> "error"       - something unexpected