You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
I’m a Dane and is therefore using LANG=da_DK.UTF-8. In Danish the decimal separator is ',' (not '.'). And for the ping-command in get_rtt_loss (utils.py) I get the following error:
ping: bad timing interval: 0.2
This is naturally because ping uses the danish language where the decimal separator is “,”. The following works at my command line:
ping -c 3 -n -i 0,2 -W 1 some_domain_or_IP_address
But it does not work with -i 0.2.
To solve this problem you frequently define LANG=C as environment
before running an external command (ping in this case).
At the moment my nordnm is working because I am feeding it the LANG=C before running nordnm. But it would be better for everybody if you change the LANG environment in get_rtt_loss (utils.py) before running the ping command.
Best regards
Jacob Tranholm
The text was updated successfully, but these errors were encountered:
I’m a Dane and is therefore using LANG=da_DK.UTF-8. In Danish the decimal separator is ',' (not '.'). And for the ping-command in get_rtt_loss (utils.py) I get the following error:
ping: bad timing interval: 0.2
This is naturally because ping uses the danish language where the decimal separator is “,”. The following works at my command line:
ping -c 3 -n -i 0,2 -W 1 some_domain_or_IP_address
But it does not work with -i 0.2.
To solve this problem you frequently define LANG=C as environment
before running an external command (ping in this case).
At the moment my nordnm is working because I am feeding it the LANG=C before running nordnm. But it would be better for everybody if you change the LANG environment in get_rtt_loss (utils.py) before running the ping command.
Best regards
Jacob Tranholm
The text was updated successfully, but these errors were encountered: