I suggest putting them all in a service group - then you can issue a force check command from the Nagios UI.
Scriot is not a bad way to go either though - the Nagios externalcommand API (via the named pipe) is easy to use and well documented. Max On 9/22/10, Brian McKee <[email protected]> wrote: > Hi All > > I'm running an old version of Nagios (2.4) > Sometimes I end up with the same service warning on multiple machines and > I'd like to force a check on all of them. > Using the web interface is a lot of clicks when it's more than just a couple > machines. > I'm thinking I should be able to gin up a for loop in bash with curl or wget > to do it for me, or am I wrong? > Does this exist already somewhere? > Pointers in the right direction appreciated > > Brian > -- > Hey, it's your computer.... isn't it? > ------------------------------------------------------------------------------ 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 [email protected] 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
