> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Rogelio Bastardo
> Sent: Monday, July 30, 2007 6:22 PM
> To: Nagios Users
> Subject: Re: [Nagios-users] check_ping vs check_icmp?
> 
> On 7/30/07, Rogelio Bastardo <[EMAIL PROTECTED]> wrote:
> > > So, if you don't mind installing the plugin setuid root, I'd
recommend
> > > using check_icmp.
> >
> > Forgive my ignorance, but where can I find this?
> >
> > (I googled for "setuid root nagios check_icmp" but nothing jumped
out at
> me)
> 
> ah, I see it's a package

Actually, this is terminology detailing how a specific set of
permissions are applied to a file/program. Basically, setuid and setgid
mean that a flag is applied to the file/program with chmod such that it
will retain it's ownership for that bit when being used. For the
purposes here, setuid root means that the file should be owned by the
user root (chown root /path/to/check_icmp) and setuid (chmod u+s
/path/to/check_icmp). This will cause check_icmp to always run as the
root user no matter who is running it. This allows it to open the
necessary socket connections without requiring that the actual root user
be running it. setuid is denoted by the 's' below --

$ ls -l /usr/local/nagios/libexec/check_icmp 
-r-sr-xr-x    1 root     nagios      15424 Jun  9 21:42
/usr/local/nagios/libexec/check_icmp

$ ls -l /bin/ping
-rwsr-xr-x    1 root     root        27860 Sep 29  2005 /bin/ping

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
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

Reply via email to