suppressing pidfile and control socket for syslog-ng 3.0
To clarify my question about suppressing PID and control socket in syslog-ng version 3.0: I don't want the error message to be suppressed by having the file successfully created in syslog-ng's favourite location, I want to suppress opening the 2 files . I might want multiple syslog-ng processes running simultaneously, for example a test instance to run without interfering with production instances. In the case of PID file, I could perhaps specify "--pidfile /dev/null" ; is there a chance that the target file might get deleted or have permissions changed? A couple of minor complaints for this option: Option --pidfile does not handle relative directories (unlike syslog-ng.conf) . Option -P responds with "Error parsing command line arguments: Unknown option -P".
Message: 3 Date: Mon, 4 May 2009 10:51:20 +0200 (CEST) From: bugzilla@bugzilla.balabit.com Subject: [syslog-ng] [Bug 43] syslog-ng 2.1.4 consumes all CPU when processing "source file" Comment #4 from Balazs Scheidler <bazsi@balabit.hu> 2009-05-04 10:51:21 [...]
can you try 3.0 if it fixes your problem? Yes, 3.0.1 on Solaris-8 fixes this problem. [...] How do I suppress pidfile and/or control socket? Error opening control socket, bind() failed; error='Permission denied (13)', socket='/local/var/run/syslog-ng.ctl' This is a different issue, you should probably create /local/var/run/ directory with appropriate permissions.
On Mon, 2009-05-04 at 11:23 -0700, Denis Laplante wrote:
To clarify my question about suppressing PID and control socket in syslog-ng version 3.0: I don't want the error message to be suppressed by having the file successfully created in syslog-ng's favourite location, I want to suppress opening the 2 files .
I might want multiple syslog-ng processes running simultaneously, for example a test instance to run without interfering with production instances.
In the case of PID file, I could perhaps specify "--pidfile /dev/null" ; is there a chance that the target file might get deleted or have permissions changed? A couple of minor complaints for this option: Option --pidfile does not handle relative directories (unlike syslog-ng.conf) . Option -P responds with "Error parsing command line arguments: Unknown option -P".
Sometimes the pidfile is being deleted, thus I do not recommend passing /dev/null as the name of the pidfile. As I see the short argument for --pidfile is small -p and not -P (it is case sensitive) I don't see why it wouldn't support relative paths, except that syslog-ng might change its current directory when going into the background. Why don't you pass two different file names for --pidfile for your two instances? Also, there are currently other things that syslog-ng which might clash if you want to run two instances: 1) persistent config file (--persist-file) 2) disk buffer files (--qdisk-dir) But otherwise it should work perfectly fine if you run two instances of it.
Message: 3 Date: Mon, 4 May 2009 10:51:20 +0200 (CEST) From: bugzilla@bugzilla.balabit.com Subject: [syslog-ng] [Bug 43] syslog-ng 2.1.4 consumes all CPU when processing "source file" Comment #4 from Balazs Scheidler <bazsi@balabit.hu> 2009-05-04 10:51:21 [...]
can you try 3.0 if it fixes your problem? Yes, 3.0.1 on Solaris-8 fixes this problem. [...] How do I suppress pidfile and/or control socket? Error opening control socket, bind() failed; error='Permission denied (13)', socket='/local/var/run/syslog-ng.ctl' This is a different issue, you should probably create /local/var/run/ directory with appropriate permissions.
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
-- Bazsi
participants (3)
-
Balazs Scheidler
-
Denis Laplante
-
okapareeya＠hotmail.com