Robert Wolfe wrote: > Hi all. My first post here. So please bear with me. > > Installed the HEAD release from the Nagios website last night and while > everything is working, I am not able to reschedule commands as I get a > message saying that the permissions on the nagios.cmd file are not correct. > What should the permissions on this file be? >
create a command grp like in the quickstart guides iirc. e.g. nagiocmd $ chmod 775 nagios/var/rw $ chown nagios:nagiocmd nagios/var/rw $ chmod g+s nagios/var/rw sticky bit for inheriting the permissions to files created below. if somebody tells you to change permissions only on nagios.cmd in var/rw/ this is only true as long as the core is running. nagios.cmd will be deleted/unlinked during core shutdown. also make sure you have put apache user into nagiocmd group. then it will have the permissions to write the nagios.cmd command file and it should work properly. Kind regards, Michael > -----Original Message----- > From: Tony Yarusso [mailto:tyaru...@nagios.com] > Sent: Thursday, September 30, 2010 6:23 PM > To: Nagios Users List > Subject: Re: [Nagios-users] significant bug in 3.2.2 - nagios.cfg -- > execute_service_checks=0 completely ignored > > On Thu, 2010-09-30 at 14:23 -0700, Mark Christian wrote: > >> dnsmichi and keith4 on IRC #nagios graciously pointed out that I need >> merely remove line 1088 from nagios 3.2.2 source base/events.c and >> recompile. I removed "run_event=TRUE;" on line 1088 of base/events.c, >> recompiled and now nagios correctly recognizes >> “execute_service_checks=0”. >> >> I believe this to be a significant bug. >> > I believe this fix has already been applied to CVS head, and is awaiting > feedback from testers of that copy before a new release is approved. If you > have a chance to try a build from CVS HEAD and report your experience the the > -devel mailing list that would be very helpful. > > -- > Tony Yarusso > Technical Team > ___ > Nagios Enterprises, LLC > Email: tyaru...@nagios.com > Web: www.nagios.com > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null -- DI (FH) Michael Friedrich Vienna University Computer Center Universitaetsstrasse 7 A-1010 Vienna, Austria email: michael.friedr...@univie.ac.at phone: +43 1 4277 14359 fax: +43 1 4277 14279 web: http://www.univie.ac.at/zid Icinga Core& IDOUtils Developer http://www.icinga.org ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
