[evlog-dev] --ANNOUNCE-- evlog-1.5.0 is available

http://evlog.sourceforge.net/

New Features:
 
   1)  A "plug-in" capability has been added so that customized 
      "event handlers" can register with evlogd to receive the 
      event stream and provide alternative processing and handling
      of event records in addition to, or instead of, the standard 
      logging/notification mechanism.  
       
   2) 2 plug-ins are provided for forwarding events from multiple 
      hosts to a centralized "event consolidation" host:
         ·  A UDP-based plug-in for "syslog-equivalent" event 
            forwarding
         ·  A TCP-based plug-in using password-authentication when 
            a more reliable protocol is desired.
      Logging of events to the local log files continues when one of
      these plug-ins is used, unless local logging is disabled. 
       
      A new evlogrmtd daemon runs on the "event consolidation host", 
      accepts events only from hosts in its evlhosts file, and passes
      them to evlogd for logging to the event consolidator's local 
      log file.  The evlogrmtd simultaneously handles events sent both
      via UDP and TCP.
       
      evlog-1.5.0 does not provide data encryption, and all of the 
      hosts must be the same architecture.  Future releases will
      provide encryption and support mixed-architecture environments.
       
   3) The evlview command now displays the hostname (local, or if
      event originated in another host, its hostname).  Also "host" 
      is a "pseudo attribute" than can be used in filter expressions.   
       
   4) Added a new user-space logging macro, syslogat(), which will 
      write a message to syslog, and based on how the format string
      is written, write additional named-attributes to the event log
      as a POSIX_LOG_PRINTF log_format event record.
    
      POSIX_LOG_PRINTF event records are new in this release, and 
      this log_format keeps the format string separated from the varargs,
      thus providing many more formatting possibilities during 
      post-processing. 
    
      A new utility, evlgentmpls, is provided which generates formatting
      templates from the .log section in .o files using syslogat().  
    
      A kernel equivalent of syslogat() for prink will be released in
      early 2003.  
 
   5) Added -q, --nmeqval option to evlview, which for records that
      have associated formatting templates, displays the non-standard 
      attributes in name=value format, one attribute per line.
       
   6) Added -F, --force to evlfacility command to not report an error
      if a facility is already in the facility registry with the correct
      facility code.
    
   7)    Several formatting template changes/additions:
      ·         support of const structs in templates
      ·         .to file names are now in hex, instead of decimal
      ·         default templates are not called default.to, instead of =1.to
      ·         if EVLTMPLPATH is not set, look in /var/evlog/$LANG before 
                /var/evlog/templates.  This allows multiple versions of a template
                to exist on a system, optionally under control of the $LANG
                environment variable (for multi-language support).
      
   8)    A HOW TO section has been added to the website.  Instructions
         are provided for:
         ·         Setting-up event logging to run in a RAM disk
         ·         (COMING SOON) Implementing an event handler plug-in
         ·         (COMING SOON)Generation and installing formatting templates using
                   syslogat() and evlgentmpls utility.


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/