Ei kuvausta

1 Haarat

Jon Schipp cdbb099ebd README: added security note		12 vuotta sitten
LICENSE	3451ba2e85 Initial commit	12 vuotta sitten
README.md	cdbb099ebd README: added security note	12 vuotta sitten
check_bro.sh	c725c68344 First commit, including plugins in repository	12 vuotta sitten
check_file_growth.sh	c725c68344 First commit, including plugins in repository	12 vuotta sitten
check_load.sh	c725c68344 First commit, including plugins in repository	12 vuotta sitten
check_ossec.sh	631dcfab0c check_ossec.sh: changed program locations for installer defaults	12 vuotta sitten
check_osx_raid.sh	c725c68344 First commit, including plugins in repository	12 vuotta sitten
check_osx_smart.sh	c725c68344 First commit, including plugins in repository	12 vuotta sitten
check_osx_temp.sh	c725c68344 First commit, including plugins in repository	12 vuotta sitten
check_service.sh	c725c68344 First commit, including plugins in repository	12 vuotta sitten
check_volume.sh	c725c68344 First commit, including plugins in repository	12 vuotta sitten

nagios-plugins

A collection of Nagios Plugins I've written for production unix environments.

A few of the scripts like check_service.sh and check_volume.sh are designed to be run in heterogenous unix environments and should work on Linux, OSX, AIX, and the BSD's provided a bash or bash-compatible shell to interpret them.

One way to run the plugins requiring elevated privileges is to configure sudo on each monitored machine to allow the nagios user to execute the plug-ins in the plug-in directory as root:

$ visudo # Use visudo to edit the sudoers file , or :
$ echo ’Defaults:nagios !requiretty ’ >> /etc/sudoers
$ echo ’nagios ALL=(root) NOPASSWD:/usr/local/nagios/libexec/∗’ >> /etc/sudoers

If that is the case be sure to limit write permissions for the scripts so that one cannot simply update the scripts with malicious code.

README.md

nagios-plugins