Dear Jan,
I just came across this issue recently:
On Tue, 11 Jul 2017 12:29:32 +0200 Jan Wagner wrote:
> <- snip ->
> Depends: inetutils-ping (>= 2:1.9-1~) [kfreebsd-any hurd-any],
> iputils-ping [linux-any],
> <- snap ->
>
> inetutils-ping and older iputils-ping (when backporting)
Hi Stefan,
Am 11.07.17 um 14:11 schrieb Stefan Bühler:
> Maybe adding a separate "ping4-command" compile time string is an option.
the problem is not the string, but the reliable detection (which
hopefully doesn't break in the feature again).
Cheers, Jan.
--
Never write mail to
Hi Jan,
On 07/11/2017 12:29 PM, Jan Wagner wrote:
> Dear Stefan,
>
> Am 11.07.17 um 11:07 schrieb Stefan Bühler:
>> You didn't get the issue. I know very well how to call check_ping with
>> -4 - I can do that with my local config. But check_ping -4 DOES NOT
>> call "ping -4" - it just calls
Dear Stefan,
Am 11.07.17 um 11:07 schrieb Stefan Bühler:
> You didn't get the issue. I know very well how to call check_ping with
> -4 - I can do that with my local config. But check_ping -4 DOES NOT
> call "ping -4" - it just calls "ping". The -4 option does *NOTHING*. It
> basically is the
Hi Jan,
On 07/11/2017 09:12 AM, Jan Wagner wrote:
> Hi Stefan,
>
> thanks for bringing this to our attention.
>
> Am 02.06.2017 um 18:39 schrieb Stefan Bühler:
>> check_ping doesn't forward the "-4" option to ping, and ping prefers
>> IPv6 now (i.e. probably whatever is configured through
Hi Stefan,
thanks for bringing this to our attention.
Am 02.06.2017 um 18:39 schrieb Stefan Bühler:
> check_ping doesn't forward the "-4" option to ping, and ping prefers
> IPv6 now (i.e. probably whatever is configured through gai.ping).
>
> Giving upstream only allows configuring
Package: monitoring-plugins-basic
Version: 2.2-3
Hi,
check_ping doesn't forward the "-4" option to ping, and ping prefers
IPv6 now (i.e. probably whatever is configured through gai.ping).
Giving upstream only allows configuring "ping-command" and
"ping6-command" (there is no explicit
7 matches
Mail list logo
