package: syslog-ng

New upstream version syslog-ng 1.6.6 released on 02/04/2005 fixes possible loss of log messages during HUP. Seems to be primarily a bugfix release.

Changelog since previous version:

2005-02-03  Balazs Scheidler  <[EMAIL PROTECTED]>

   * src/sources.c (do_read_line): added a notification about
   messages exceeding log_msg_size()

   * doc/sgml/syslog-ng.sgml: clarified a paragraph on klogd

   * doc/syslog-ng.8: fixed another typo (by Jose Pedro Oliveira)

   * contrib/syslog2ng: fixed typo in emerg generation (by Jose Pedro
   Oliveira)

2005-01-31  Balazs Scheidler  <[EMAIL PROTECTED]>

   * contrib/relogger.pl: new script by Ed Ravin to replay syslog
   messages from a logfile

2005-01-30  Balazs Scheidler  <[EMAIL PROTECTED]>

   * doc/man/syslog-ng.8: updated manpage (patch by Jose Pedro
   Oliveira)

2005-01-21  Balazs Scheidler  <[EMAIL PROTECTED]>

   * configure.in: added patch to link against various libs
   statically

2005-01-20  Balazs Scheidler  <[EMAIL PROTECTED]>

   * src/main.c: fix possible log message losing during HUP as
   syslog-ng was not accepting messages for 1 second and these
   messages were dropped, processing changed so we still wait 1
   second to flush buffers but also accept messages in this interval,
   so the window of losing messages becomes much smaller. (fixes:
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282771)

2004-12-13  Balazs Scheidler  <[EMAIL PROTECTED]>

   * src/macros.gprf: added PRI macro

2004-11-18  Balazs Scheidler  <[EMAIL PROTECTED]>

   * src/main.c (main): some platform seems to require that a tzset()
   is run at startup

   * src/afprogram.c: call setsid() in the forked program to make the
   subshell part of another process group to avoid the termination of
   syslog-ng when someone invokes a kill 0 there. Fixes a program()
   related problem in OpenBSD 3.5

2004-09-17  Balazs Scheidler  <[EMAIL PROTECTED]>

   * cfg-grammar.y: added log_fifo_size option to TCP/UDP
   destinations



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to