Thanks alot Gergely!! I really appreciate the response.<br><br>I am using the example file and see the OPTIONS variable. The -p option is valid, but the -c option does not appear to be. I checked in the syslog-ng Open Source Edition 3.1 Administrator Guide and the man page. There is a -C for the chroot directory, but I don't think that is what you are referring to. Course it is always possible the documentation is not updated. Have you used the -c before?<br>
<br>Also, any thoughts as to why I cannot find the syslog-ng.pid file anywhere on the system? All of the startup/shutdown scripts use it and syslog-ng is running. This really has me scratching my head:))<br><br>Thanks!!<br>
<br><div class="gmail_quote">On Mon, Apr 25, 2011 at 3:08 PM, Gergely Nagy <span dir="ltr"><<a href="mailto:algernon@balabit.hu" target="_blank">algernon@balabit.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div><div></div><div>Zeek Anow <<a href="mailto:zeekstern@gmail.com" target="_blank">zeekstern@gmail.com</a>> writes:<br>
<br>
> We are running Solaris 10 Update 9, syslog-ng 3.1.2 - version details<br>
> at bottom of this msg.<br>
><br>
> I wanted the syslog-ng.pid file to be located in swap so it would be<br>
> cleared after a reboot.<br>
> I also did not like the idea of creating the /usr/local/var/run<br>
> directories, so:<br>
><br>
> I modified the /lib/svc/method file and then validated and imported<br>
> the syslog-ng.xml file.<br>
> I stopped/disabled the syslog-ng process to make this change.<br>
><br>
> So now, I have 3 problems, but syslog-ng is running, and I can't<br>
> imagine how:)).<br>
><br>
> 1. I cannot find the 2 files syslog-ng.pid or syslog-ng.ctl files<br>
> anywhere on the system.<br>
> I did a global find which searches the entire disk.<br>
><br>
> 2. When syslog-ng started up, I got the following msg, and it is true:<br>
> Error opening control socket, bind() failed; socket='/usr/local/var/syslog-<br>
> ng.ctl', error='No such file or directory.<br>
><br>
> 3. Before I made the change, a ps was showing:<br>
> root 5769 1 7 7 0 Apr 21 ? 0:00<br>
> /usr/local/sbin/syslog-ng<br>
> root 5770 5769 5770 5770 13 Apr 21 ? 5618:33<br>
> /usr/local/sbin/syslog-ng<br>
><br>
> cat /usr/local/var/syslog-ng.pid<br>
> 5770<br>
><br>
> As you can see, the PID is 5770. Shouldn't that be 5769??<br>
<br>
</div></div>The problem is, according to the error message you quoted above, is that<br>
syslog-ng is trying to put its pidfile and the control socket to the<br>
location that was specified at build time.<br>
<br>
To override that, you can change the method file to actually pass the<br>
$PIDFILE to syslog-ng. It seems to me, that it doesn't do that, and only<br>
uses the PIDFILE option for itself.<br>
<br>
If you change the syslog-ng invocation in that method file to run<br>
syslog-ng with the -p $PIDFILE and -c /path/to/syslog-ng.ctl parameters,<br>
that should do the trick.<br>
<br>
If you're using the method file that comes with syslog-ng, then if you<br>
add the two parameters I mentioned earlier to the OPTIONS variable, that<br>
should do just what you want.<br>
<font color="#888888"><br>
--<br>
|8]<br>
<br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.campin.net/syslog-ng/faq.html" target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
<br>
</font></blockquote></div><br>