[
https://issues.apache.org/jira/browse/ARTEMIS-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732190#comment-16732190
]
Laurent Bigonville commented on ARTEMIS-2219:
---------------------------------------------
The other implementation I can find in debian is inetutils and with
implementation of ping, the -t parameter if for "type".
iputils:
-w deadline
Specify a timeout, in seconds, before ping exits regardless of how
many packets have been sent or received. In this case ping does not stop after
count packet are sent, it waits either for
deadline expire or until count probes are answered or for some error
notification from network.
-W timeout
Time to wait for a response, in seconds. The option affects only
timeout in absence of any responses, otherwise ping waits for two RTTs.
inetutils:
-w, --timeout=N
stop after N seconds
-W, --linger=N
number of seconds to wait for response
> Default configuration and documentation for network-check-ping-command mix
> TTL and timeout
> ------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2219
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2219
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Laurent Bigonville
> Priority: Major
>
> Hello,
> "ping -c 1 -t %d %s" is used as the default configuration and examples in the
> documentation for the network-check-ping-command parameter.
> If I'm not wrong, %d is replaced by the value of network-check-timeout
> BUT, the -t command of ping (or at least the recent implementation from
> iputils) is the parameter for the TTL, not the timeout. The parameter for the
> timeout is -W
> AFAICS, at least RHEL and debian (and derivatives) are using ping from
> iputils, so this should be changed in the default configuration, or at least
> a note should be added in the documentation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
