[syslog-ng]preparing syslog-ng 1.6.6

[Balazs Scheidler]

On Mon, 2005-01-31 at 20:33 +0000, José Pedro Oliveira wrote:
> > As there are some changes since syslog-ng 1.6.5, I'd like to release a
> > new version. Before doing so I'd like to ask you to test the latest
> > snapshot a little bit. The most important and risky change seems to be
> > this one:
> > 
> > 2005-01-20  Balazs Scheidler  <bazsi@bzorp.balabit>
> > 
> >         * 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)
> > 
> > Everything else is minor, and although they might cause build problems 
> > on some platforms, I doubt they'd cause real problems.
> 
> The above patch corrected the out of order messages when handling the
> SIGHUP signal:
> 
>     ...
>     Sep 30 20:35:58 pateta syslog-ng[1858]: STATS: dropped 0
>     Sep 30 20:45:58 pateta syslog-ng[1858]: STATS: dropped 0
>  >> Sep 30 20:51:06 pateta syslog-ng[1858]: new configuration initialized
>  >> Sep 30 20:51:05 pateta syslog-ng[1858]: SIGHUP received, restarting
>     syslog-ng
>     Sep 30 21:01:06 pateta syslog-ng[1858]: STATS: dropped 0
>     ...
> 
> Previously reported in:
> https://lists.balabit.hu/pipermail/syslog-ng/2004-September/006416.html

Yes, the "SIGHUP received" message was delayed until the new
configuration was initialized.

> 
> > The latest snapshot is here:
> > 
> > http://www.balabit.com/downloads/syslog-ng/1.6/src-snapshot/
> > 
> > The summary of changes can be found in the file named ChangeLog within 
> > the tarball. If no show-stopper bugs are found, I'm going to release 
> > syslog-ng 1.6.6 this week.
> 
> There is a small error in the Changelog.  The 2004-08-05 entry reports
> that syslog-ng 1.6.5 needs libol version 0.3.15.  It should be libol
> version 0.3.14 (not 0.3.15).

Fixed.


-- 
Bazsi