-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Datetime with -Q behaves strangely #203
Comments
It is reproducible on FreeBSD 12.2-RELEASE-p2, too but not on Debian 10.7 FreeBSD
Debian
|
At the build process the compiler don't set the macro
|
I'm not realy happy with this solution. But I have two other conception.
|
I have create a new version that fix the issue over configure.ac |
Definitely would appreciate this making it upstream as macOS and FreeBSD are my primary OSes. Edit: It looks like 04af04c resolve may have resolved this. |
this should be fixed in fping 5.1 |
Thank you! 👍 |
Change update_current_time() so that current_time is set from CLOCK_REALTIME and current_time_ms is set from CLOCK_MONOTONIC. This way log messages display wall clock time while any timing calculations use monotonic time. See schweikert#203 In seqmap_add(), before checking to see if .time_ts wrapped, check that .time_ts was set. See schweikert#288
Change update_current_time() so that current_time is set from CLOCK_REALTIME and current_time_ms is set from CLOCK_MONOTONIC. This way log messages display wall clock time while any timing calculations use monotonic time. See schweikert#203 In seqmap_add(), before checking to see if .time_ts wrapped, check that .time_ts was set. See schweikert#288
Change update_current_time() so that current_time is set from CLOCK_REALTIME and current_time_ms is set from CLOCK_MONOTONIC. This way log messages display wall clock time while any timing calculations use monotonic time. See schweikert#203 In seqmap_add(), before checking to see if .time_ts wrapped, check that .time_ts was set. See schweikert#288
Some changes of fping resulted in some systems reporting implausible timestamps, see, e.g., GH issue schweikert#203. This commit adds a simplistic plausability check for timestamps in Unix time format: they need to be greater or equal to 1000000000 (2001-09-09 03:46:40+02:00).
Some changes of fping resulted in some systems reporting implausible timestamps, see, e.g., GH issue schweikert#203. This commit adds a simplistic plausability check for timestamps in Unix time format: they need to be greater or equal to 1000000000 (2001-09-09 03:46:40+02:00).
Some changes of fping resulted in some systems reporting implausible timestamps, see, e.g., GH issue schweikert#203. This commit adds a simplistic plausability check for timestamps in Unix time format: they need to be greater or equal to 1000000000 (2001-09-09 03:46:40+02:00).
Some changes of fping resulted in some systems reporting implausible timestamps, see, e.g., GH issue #203. This commit adds a simplistic plausability check for timestamps in Unix time format: they need to be greater or equal to 1000000000 (2001-09-09 03:46:40+02:00).
Hi,
I am running this program at
02:27
(at night/early morning) however the output from fping believes it is14:42
, first I thought it interpreted02:
as14:
, but the minutes are also off by 15 minutes compared to the system clock:Version
Installed through Homebrew on OSX Catalina.
The text was updated successfully, but these errors were encountered: