Hi all, I have an application that I would like to send all syslog messages to via an AF_UNIX/SOCK_DGRAM socket. I declared a unix-dgram destination in my syslog-ng.conf file and have configured syslog-ng so that it logs all messages to that destination. Everything works fine as long as my application is running before syslog-ng starts up. If I try to start up syslog-ng before my application, I get the following error message Re-Staring syslog servicesError connecting to AF_UNIX(/tmp/.mysock): Bad file descriptor and syslog-ng exits with an error. Is there any way I can have syslog-ng start before my application with a unix-dgram destination? Or am I just missing something obvious? BTW, I am using syslog-ng-1.6.8 Thanks in advance for any help with this... Tom
Can you check if the latest 1.9.x snapshot has the same behaviour? On Wed, 2006-02-22 at 13:31 -0800, Tom Morano wrote:
Hi all,
I have an application that I would like to send all syslog messages to via an AF_UNIX/SOCK_DGRAM socket. I declared a unix-dgram destination in my syslog-ng.conf file and have configured syslog-ng so that it logs all messages to that destination. Everything works fine as long as my application is running before syslog-ng starts up. If I try to start up syslog-ng before my application, I get the following error message
Re-Staring syslog servicesError connecting to AF_UNIX(/tmp/.mysock): Bad file descriptor
and syslog-ng exits with an error.
Is there any way I can have syslog-ng start before my application with a unix-dgram destination? Or am I just missing something obvious?
-- Bazsi
participants (2)
-
Balazs Scheidler
-
Tom Morano