[syslog-ng]Problem after HANGUP signal

[Jerome Poggi]

On Thu, 18 Oct 2001, Mark Borges wrote:

> >> Balazs Scheidler(BS) wrote:
...
> BS> if you send a HUP signal, syslog-ng doesn't write STATS: messages? that must
> BS> be a bug.
> 
> Is that bug related to this bug?
>
>   prw-r-----    1 foo      other  0 Oct 16 15:54 /tmp/syslog.fifo
>   $ kill -HUP 23692
>   p---------    1 foo      other  0 Oct 16 15:54 /tmp/syslog.fifo
> 
> i.e., sending HUP evidently chmod's the named pipe that syslog-ng uses
> as a source to an un-usable permission.
I can't say if it the same bug, because I don't have the fifo file.
But apparatly it's a very similar.
> 
> This is with syslog-ng-1.5.11, libol-0.3.0, running under Solaris-2.6,
> built with gcc-2.95.3.
For me it's on Linux 2.4.10 with syslog-ng-1.5.11, libol-0.3.0 and
gcc-2.95.3.

--
Jerome POGGI                                     Jerome.Poggi@hsc.fr
Herve Schauer Consultants       -=-      Network Security Consultant
http://www.hsc.fr/                             Tel : +33 141 409 700