Sort of nginx specific...
iberkner at gmail.com
Mon Oct 4 16:11:21 MSD 2010
That's a valid point and I'm pretty sure that's exactly what it was as once
I fixed that issue, it worked.
On Mon, Oct 4, 2010 at 7:20 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> On Sun, Oct 03, 2010 at 01:39:59PM -0400, Ilan Berkner wrote:
> > Hi All,
> > I'm setting up Nagios to run thorugh Nginx. I have the CGI wrapper
> > (yey). However, some nagios web based functions require access to a
> > command file (a pipe) in the nagios /var/rw directory.
> > When the nagios service starts, it creates a "nagios.cmd" pipe file in
> > rw directory.
> > When trying to access that web file through the web interface, there's a
> > permission issue. However, if I set the nagios.cmd file to have 777
> > permissions, it works fine.
> > The problem is that when the nagios service is restarted, the nagios.cmd
> > file is recreated and no longer has the 777 permissions.
> > I am running the nagios service and the Nginx web server under the same
> > and group.
> nginx user doesn't matter as nginx only talks to backend (i.e.
> your CGI wrapper). It's your CGI wrapper user/group which
> Maxim Dounin
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx