You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/06/04 12:29:00 UTC
[jira] [Commented] (ARTEMIS-2792) Wrong default network pinger
command for linux
[ https://issues.apache.org/jira/browse/ARTEMIS-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125882#comment-17125882 ]
ASF subversion and git services commented on ARTEMIS-2792:
----------------------------------------------------------
Commit 1ee0bbf34cd3a8b9ac5994bd9195fb2c0511cbdc in activemq-artemis's branch refs/heads/master from brusdev
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1ee0bbf ]
ARTEMIS-2792 Fix default network pinger command for linux
> Wrong default network pinger command for linux
> ----------------------------------------------
>
> Key: ARTEMIS-2792
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2792
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Domenico Bruscino
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The network pinger uses a network timeout as an argument for -t in the ping command.
> The linux man page for ping says -t sets TTL, which is "The TTL value of an IP packet represents the maximum number of IP routers that the packet can go through before being thrown away. In current practice you can expect each router in the Internet to decrement the TTL field by exactly one."
> It looks like the intent was to use -w timeout, in seconds, before ping exits regardless of how many packets have been sent or received.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)