Lucas Fritz wrote: > > Nagios-Users, > > Are there any definitive guides for monitoring a remote OSX 10.4 Server? > > Ideally I’d like to do a minimum of configuration on the remote server > and looking at the guide located here: > > http://nagios.sourceforge.net/docs/nrpe/NRPE.pdf > > I’m not convinced this will work for installation on OSX. > > Has anyone done this before? Are there any caveats or alterations to > these instructions necessary for this to work on OSX? > > Thank you very much for any help you can provide, > > Lucas > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > 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 Depending on what you want to monitor, snmp is likely your best bet. AFAIK, there's no gui for snmp on OSX, so you'll need to dive in to get it setup and running, but much is exposed, and there are various snmp based plugins available for Nagios.
tim ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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