|
From: Michael J. P. <mi...@ae...> - 2005-02-08 23:35:46
|
It needs to have a SUID of root. In case you are like me and new to = Linux you do that by; Chown root check_icmp Chgrp root check_icmp Chmod u+s check_icmp Chmod g+s check_icmp Of course there might be a quicker way to do that.. Michael J. Prentice AEC One Stop Group Inc. Phone (954) 255-4359 -----Original Message----- From: nag...@li... = [mailto:nag...@li...] On Behalf Of Lewis = Getschel Sent: Tuesday, February 08, 2005 6:21 PM To: nag...@li... Subject: Re: [Nagios-users] check_icmp All- I just compiled check_icmp 1.0 (as myself) and for users other than=20 root I get: Failed to obtain ICMP socket: Operation not permitted First as myself, second with sudo > ./check_icmp masterserver002 check_icmp: Failed to obtain ICMP socket: Operation not permitted > sudo ./check_icmp masterserver002 OK - masterserver002: rta 0.229ms, lost=20 0%|rta=3D0.229ms;200.000;500.000;0; pl=3D0%;40;80;; > Any suggestions for me to resolve this? Thanks, Lewis Andreas Ericsson wrote: > Bergstr=F6m Sebastian wrote: > >> Andreas Ericsson, I know you're involved in this so perhaps you could >> give me an answer? Anyone is encouraged to answer of course :o) >> > > Being the original author, I think I can. > >> I'm trying to find information about the check_icmp plugin for >> Nagios. Some e-mails in the past has touched this but I'm not getting >> the complete picture. Is there any webpage or other information >> channel that shows progress on the check_icmp development and perhaps >> some of it's benefits over check_ping (I assume _icmp is to replace >> _ping?). Some documentation like switches would be handy as well. >> >> Thanks in advance! >> > > check_icmp is included in the official plugin package as a drop-in=20 > replacement for check_ping. check_icmp -h provides the necessary help=20 > output. > > The latest version of check_icmp (as coded by my humble self) is=20 > available at https://devel.op5.se/oss or http://oss.op5.se/nagios as=20 > check_icmp-<version>.tar.gz. Be aware that the code might change=20 > without version increment while I'm researching a weird network error=20 > on *bsd (most likely a kernel issue, but it's hard to know for sure),=20 > although only for fixing this particular bug. Look for the mtime as=20 > provided by apache to find out if it is indeed a new release or not (a = > fresh one just hatched 2 seconds ago, actually). > >> >> Best regards, Sebastian Bergstroem >> >> ---------------------------------------------- Sebastian Bergstroem=20 >> Technical coordinator Kunskapsskolan i Sverige AB=20 >> seb...@ku...=20 >> ----------------------------------------------- >> >> >> ------------------------------------------------------- SF email is >> sponsored by - The IT Product Guide Read honest & candid reviews on >> hundreds of IT Products from real users. Discover which products >> truly live up to the hype. Start reading now.=20 >> http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dclick=20 >> _______________________________________________ Nagios-users mailing >> list Nag...@li...=20 >> 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 >> > --=20 Lewis Getschel | Today is done... WesternGeco | Today was fun... 1625 Broadway | Tomorrow is another one. Denver, CO 80202 | Direct Phone - 303-389-4407| -- Dr. Seuss -- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dick _______________________________________________ Nagios-users mailing list Nag...@li... https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when = reporting any issue.=20 ::: Messages without supporting info will risk being sent to /dev/null |