> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Peter Blair > Sent: Friday, June 23, 2006 4:02 PM > To: Joco Salvatti > Cc: Misc OpenBSD > Subject: Re: Nagios and Apache > > Obvious, but ensure that /var/www/cgi-bin/nagios is a valid directory > from the perspective of your chroot'd server. >
I would say that it is a valid directory... it was on my installation. Isn't /var/www/cgi-bin a valid chroot directory by definition? > Another caveat is to ensure that the named pipe is accessable to both > the nagios executable, and to the chroot'd cgi's (once they start > working that is). Nagios references the pipe via absolute naming, so > you may have to 'break' things a bit and create a symlink under your > chroot directory of "/usr/local/nagios/rw/nagios.cmd" that points to > the actual pipe. > > Also, try turning off chroot to see if that helps. That will at the > least tell you if it's a visibility issue or not. > I think if you turn off chroot then the other parts of the program that depend on the chroot'd directory structure will break when you un-chroot it... right? Dan Farrell Applied Innovations [EMAIL PROTECTED]
