ping: bad timing interval: 0.5 #273
Comments
|
Lets see. Ok, all lost. How about pinging something that does answer. I do not think there is anything wrong with ping. |
|
can you: ping 192.168.13.1 -i 0.5 -c 3 |
|
Strange, on my computer, ping 127.0.0.1 -i 0.5 -c 3 Maybe Lubuntu issue. |
|
real crazy! I don't know what happened to my system....
|
|
After I change "Region & Language" --> "Fromats" from Belgien to United States. The issue disappear. |
|
First, for checking these language / locale / i18n problems please use localhost address, which is always available:
But for Czech it's I consider having |
|
It is the default ping from ubuntu20 LTS: ping from iputils s20190709 |
pevik
added a commit
to pevik/iputils
that referenced
this issue
Aug 10, 2020
Handling -i and -W parameter changed over the time, recently introducing several *incompatible* changes: * -i interval option Until s20121114 ping used '.' (dot) as a decimal separator. Then in 04d3f79 ("ping,ping6: Do not assume radix point is denoted by '.' (-i option).") released in s20121121 decided to use decimal point from locales (depended on $LC_NUMERIC). But even then it depend on USE_IDN=yes which does not make much sense. Recently d865d4c ("ping: Use C locale for parsing -i/-W without IDN") addressed that and called setlocale() unconditionally. Maybe condition based on ENABLE_NLS definition should have been discussed, but that would probably lead just to LC_ALL=C setup in the scripts. People also get confused by old behavior when decimal separator depends on locale as some distros e.g. compile without IDN but other don't (see issue iputils#273) But that introduced *incompatible* behavior for next release, thus documenting it in this commit. 562e0d5 fixed problems for -W, but also introduced yet another *incompatible* behavior as invalid number is no longer fatal error (see below). d196177 ("ping: Add missing preprocesses checks around setlocale() calls") unintentionally restored the old behavior, which was fixed by 7a90bd5 ("ping: Fix handling decimal separator for -i/-W opt"). * -W timeout option Until s20180629 there was undocumented behavior: 1) timeout silently rounded down to the next lower integral number 2) -W N for N < 1 was rounded to 0 => infinite timeout (obviously a bug) 3) -W Ns worked as expected (sleep for N sec, as 's' was dropped, this could be considered as a feature) 4) -W Nm -W Nh also slept for N sec instead of N min or hour (obviously a bug) 918e824 ("ping: add support for sub-second timeouts") released in s20190324 fixed 1) and 2) by allowing real number with locale based decimal separator when USE_IDN=yes configured. But that introduced *incompatible* behavior as broke 3 and 4). As it was not documented in release notes, people complained (issue iputils#236). 562e0d5 ("ping: allow -i and -W option arguments contain garbage input") restored 3) and 4) support (everything including and after first non-numeric character is dropped, warning printed). Fixes: iputils#290 Signed-off-by: Petr Vorel <pvorel@suse.cz>
pevik
added a commit
to pevik/iputils
that referenced
this issue
Aug 10, 2020
Handling -i and -W parameter changed over the time, recently introducing several *incompatible* changes: * -i interval option Until s20121114 ping used '.' (dot) as a decimal separator. Then in 04d3f79 ("ping,ping6: Do not assume radix point is denoted by '.' (-i option).") released in s20121121 decided to use decimal point from locales (depended on $LC_NUMERIC). But even then it depend on USE_IDN=yes which does not make much sense. Recently d865d4c ("ping: Use C locale for parsing -i/-W without IDN") addressed that and called setlocale() unconditionally. Maybe condition based on ENABLE_NLS definition should have been discussed, but that would probably lead just to LC_ALL=C setup in the scripts. People also get confused by old behavior when decimal separator depends on locale as some distros e.g. compile without IDN but other don't (see issue iputils#273) But that introduced *incompatible* behavior for next release, thus documenting it in this commit. 562e0d5 fixed problems for -W, but also introduced yet another *incompatible* behavior as invalid number is no longer fatal error (see below). d196177 ("ping: Add missing preprocesses checks around setlocale() calls") unintentionally restored the old behavior, which was fixed by previous commit 7a90bd5 ("ping: Fix handling decimal separator for -i/-W opt"). * -W timeout option Until s20180629 there was undocumented behavior: 1) timeout silently rounded down to the next lower integral number 2) -W N for N < 1 was rounded to 0 => infinite timeout (obviously a bug) 3) -W Ns worked as expected (sleep for N sec, as 's' was dropped, this could be considered as a feature) 4) -W Nm -W Nh also slept for N sec instead of N min or hour (obviously a bug) 918e824 ("ping: add support for sub-second timeouts") released in s20190324 fixed 1) and 2) by allowing real number with locale based decimal separator when USE_IDN=yes configured. But that introduced *incompatible* behavior as broke 3 and 4). As it was not documented in release notes, people complained (issue iputils#236). 562e0d5 ("ping: allow -i and -W option arguments contain garbage input") restored 3) and 4) support (everything including and after first non-numeric character is dropped, warning printed). Fixes: iputils#290 Signed-off-by: Petr Vorel <pvorel@suse.cz>
pevik
added a commit
to pevik/iputils
that referenced
this issue
Aug 18, 2020
Handling -i and -W parameter changed over the time, recently introducing several *incompatible* changes: * -i interval option Until s20121114 ping used '.' (dot) as a decimal separator. Then in 04d3f79 ("ping,ping6: Do not assume radix point is denoted by '.' (-i option).") released in s20121121 decided to use decimal point from locales (depended on $LC_NUMERIC). But even then it depend on USE_IDN=yes which does not make much sense. Recently d865d4c ("ping: Use C locale for parsing -i/-W without IDN") addressed that and called setlocale() unconditionally. Maybe condition based on ENABLE_NLS definition should have been discussed, but that would probably lead just to LC_ALL=C setup in the scripts. People also get confused by old behavior when decimal separator depends on locale as some distros e.g. compile without IDN but other don't (see issue iputils#273) But that introduced *incompatible* behavior for next release, thus documenting it in this commit. 562e0d5 fixed problems for -W, but also introduced yet another *incompatible* behavior as invalid number is no longer fatal error (see below). d196177 ("ping: Add missing preprocesses checks around setlocale() calls") unintentionally restored the old behavior, which was fixed by previous commit 7a90bd5 ("ping: Fix handling decimal separator for -i/-W opt"). * -W timeout option Until s20180629 there was undocumented behavior: 1) timeout silently rounded down to the next lower integral number 2) -W N for N < 1 was rounded to 0 => infinite timeout (obviously a bug) 3) -W Ns worked as expected (sleep for N sec, as 's' was dropped, this could be considered as a feature) 4) -W Nm -W Nh also slept for N sec instead of N min or hour (obviously a bug) 918e824 ("ping: add support for sub-second timeouts") released in s20190324 fixed 1) and 2) by allowing real number with locale based decimal separator when USE_IDN=yes configured. But that introduced *incompatible* behavior as broke 3 and 4). As it was not documented in release notes, people complained (issue iputils#236). 562e0d5 ("ping: allow -i and -W option arguments contain garbage input") restored 3) and 4) support (everything including and after first non-numeric character is dropped, warning printed). Fixes: iputils#290 Signed-off-by: Petr Vorel <pvorel@suse.cz>
pevik
added a commit
that referenced
this issue
Aug 18, 2020
Handling -i and -W parameter changed over the time, recently introducing several *incompatible* changes: * -i interval option Until s20121114 ping used '.' (dot) as a decimal separator. Then in 04d3f79 ("ping,ping6: Do not assume radix point is denoted by '.' (-i option).") released in s20121121 decided to use decimal point from locales (depended on $LC_NUMERIC). But even then it depend on USE_IDN=yes which does not make much sense. Recently d865d4c ("ping: Use C locale for parsing -i/-W without IDN") addressed that and called setlocale() unconditionally. Maybe condition based on ENABLE_NLS definition should have been discussed, but that would probably lead just to LC_ALL=C setup in the scripts. People also get confused by old behavior when decimal separator depends on locale as some distros e.g. compile without IDN but other don't (see issue #273) But that introduced *incompatible* behavior for next release, thus documenting it in this commit. 562e0d5 fixed problems for -W, but also introduced yet another *incompatible* behavior as invalid number is no longer fatal error (see below). d196177 ("ping: Add missing preprocesses checks around setlocale() calls") unintentionally restored the old behavior, which was fixed by previous commit 7a90bd5 ("ping: Fix handling decimal separator for -i/-W opt"). * -W timeout option Until s20180629 there was undocumented behavior: 1) timeout silently rounded down to the next lower integral number 2) -W N for N < 1 was rounded to 0 => infinite timeout (obviously a bug) 3) -W Ns worked as expected (sleep for N sec, as 's' was dropped, this could be considered as a feature) 4) -W Nm -W Nh also slept for N sec instead of N min or hour (obviously a bug) 918e824 ("ping: add support for sub-second timeouts") released in s20190324 fixed 1) and 2) by allowing real number with locale based decimal separator when USE_IDN=yes configured. But that introduced *incompatible* behavior as broke 3 and 4). As it was not documented in release notes, people complained (issue #236). 562e0d5 ("ping: allow -i and -W option arguments contain garbage input") restored 3) and 4) support (everything including and after first non-numeric character is dropped, warning printed). See also: #290 Signed-off-by: Petr Vorel <pvorel@suse.cz>
David-Lor
added a commit
to David-Lor/ping2mqtt
that referenced
this issue
May 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ping 192.168.13.1 -i 0.5
version:
ping -V
ping from iputils s20190709
The text was updated successfully, but these errors were encountered: