[Nagiosplug-devel] [ nagiosplug-Bugs-1637767 ] check_ping 1.4.5 on FreeBSD 5.4 fails

[SourceForge.net]

Bugs item #1637767, was opened at 2007-01-17 06:33
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1637767&group_id=29880

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General plugin execution
Group: Release (specify)
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Pentarh Udi (pentarh)
Assigned to: Nobody/Anonymous (nobody)
Summary: check_ping 1.4.5 on FreeBSD 5.4 fails

Initial Comment:
Says "Could not open pipe: " for any command arguments.

After some researching I found that "configure" script did not created appropriate defines as well. It only created

#define PING_COMMAND=""

So after patching config.h, removing the define above and placing following defines i get it worked:

#define PING_COMMAND "/sbin/ping -t %u -c %u %s"
#define PING_HAS_TIMEOUT
#define PING_PACKETS_FIRST

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2007-06-19 19:20

Message:
Logged In: YES 
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Holger Weiss (hweiss)
Date: 2007-06-05 08:29

Message:
Logged In: YES 
user_id=759506
Originator: NO

Errm, we are aware of "--with-ping-command", but we were trying to fix a
problem you reported! :-)  PING_COMMAND should be set correctly
out-of-the-box.  If this doesn't happen, that would be a bug.

And it definitely makes sense to fix bugs not only within some OS-specific
package/port, but also upstream in order to make life easier for the
package/port maintainer and for people who install the plugins manually for
some reason.

I set the status back to 'pending'.

Holger

----------------------------------------------------------------------

Comment By: Pentarh Udi (pentarh)
Date: 2007-06-05 08:19

Message:
Logged In: YES 
user_id=1694463
Originator: YES

There is a configure option --with-ping-command or something similar. You
can check it via "./configure --help".

Also I suggest to install it from FreeBSD ports - there are no problems.

----------------------------------------------------------------------

Comment By: Holger Weiss (hweiss)
Date: 2007-06-05 08:05

Message:
Logged In: YES 
user_id=759506
Originator: NO

Good idea IMO.

Holger

----------------------------------------------------------------------

Comment By: Matthias Eble (psychotrahe)
Date: 2007-06-05 08:04

Message:
Logged In: YES 
user_id=1694341
Originator: NO

sbin is in $PATH by default at least on my freebsd 6.2 box.

Should we consider to add the common pathes like /bin, /usr/bin, /sbin,
and /usr/sbin to 
the configure script (after searching $PATH)?

Matthias

----------------------------------------------------------------------

Comment By: Holger Weiss (hweiss)
Date: 2007-06-05 07:07

Message:
Logged In: YES 
user_id=759506
Originator: NO

I cannot reproduce this on a FreeBSD 5.5-STABLE (2006-11-06) box, neither
with check_ping 1.4.5 nor with 1.4.9:

$ ./configure
$ grep PING_COMMAND config.h
#define PING_COMMAND "/sbin/ping -n -c %d %s"

I _can_ of course reproduce the problem if I remove /sbin from my $PATH
prior to "./configure", though.  I'd guess this was the problem here.

Please let us know whether you can still reproduce the problem with
check_ping 1.4.9 and after verifying that your $PATH includes "/sbin".  For
the moment, I set the status of the bug report to 'pending', which means
that it'll be closed automatically if we don't get further feedback.

Thanks a lot, Holger

----------------------------------------------------------------------

Comment By: Matthias Eble (psychotrahe)
Date: 2007-06-05 04:25

Message:
Logged In: YES 
user_id=1694341
Originator: NO

I tried this with freebsd 6.2 but cannot reproduce the problem.
Has anyone of the devs got a freebsd 5.4 box up and running?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1637767&group_id=29880