That's a valid point and I'm pretty sure that's exactly what it was as once I fixed that issue, it worked.<div><br></div><div>Thanks!<br><br><div class="gmail_quote">On Mon, Oct 4, 2010 at 7:20 AM, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello!<br>
<div class="im"><br>
On Sun, Oct 03, 2010 at 01:39:59PM -0400, Ilan Berkner wrote:<br>
<br>
> Hi All,<br>
><br>
> I'm setting up Nagios to run thorugh Nginx. I have the CGI wrapper working<br>
> (yey). However, some nagios web based functions require access to a nagios<br>
> command file (a pipe) in the nagios /var/rw directory.<br>
><br>
> When the nagios service starts, it creates a "nagios.cmd" pipe file in the<br>
> rw directory.<br>
><br>
> When trying to access that web file through the web interface, there's a<br>
> permission issue. However, if I set the nagios.cmd file to have 777<br>
> permissions, it works fine.<br>
><br>
> The problem is that when the nagios service is restarted, the nagios.cmd<br>
> file is recreated and no longer has the 777 permissions.<br>
><br>
> I am running the nagios service and the Nginx web server under the same user<br>
> and group.<br>
<br>
</div>nginx user doesn't matter as nginx only talks to backend (i.e.<br>
your CGI wrapper). It's your CGI wrapper user/group which<br>
matters.<br>
<br>
Maxim Dounin<br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://nginx.org/mailman/listinfo/nginx" target="_blank">http://nginx.org/mailman/listinfo/nginx</a><br>
</blockquote></div><br></div>