Is it possible to make syslog-ng keep a socket open? A developer has some perl code that passes a message to syslog-ng, which opens a socket, sends the message along, then closes the socket. Data that he attempts to write to the same socket isn't written because syslog-ng has already closed the socket. Any help is appreciated. -Adam