Hi all Can you please tell me what happens when syslog-ng reloads (i.e. receives HUP signal) ? I need to know what signal does it send to the destination programs, and is it a good practice to catch this signal. In fact I don't want my destination program to die at reload, or at least I want to serialize his data structures before it dies, in order to retrieve it when it goes back. On the other hand, if a message arrives from an UDP source while syslog-ng is reloading, will it be lost ? Why the keep alive option is only for tcp source ? Thanks a lot for any help Ali
Ali EL MOUSSAWI <alinxb@yahoo.fr> - Thu, Sep 23, 2004:
Why the keep alive option is only for tcp source ?
This is because keep alives only make sense on connection-oriented sockets. This is explained in socket(7). -- Loïc Minier <lool@dooz.org>
On Thu, 2004-09-23 at 16:01, Loïc Minier wrote:
Ali EL MOUSSAWI <alinxb@yahoo.fr> - Thu, Sep 23, 2004:
Why the keep alive option is only for tcp source ?
This is because keep alives only make sense on connection-oriented sockets. This is explained in socket(7).
not really, the keep-alive option has nothing to do with TCP keep-alives, it simply means the socket will not be closed/reopened during a HUP. In this sense it should be possible to do the same with UDP sockets. I'll add a bugzilla entry on that. -- Bazsi
participants (3)
-
Ali EL MOUSSAWI
-
Balazs Scheidler
-
Loïc Minier