[Bug 283256] CLOCK_MONOTONIC in dhclient
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283256] CLOCK_MONOTONIC in dhclient"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283256] CLOCK_MONOTONIC in dhclient"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283256] CLOCK_MONOTONIC in dhclient"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283256] CLOCK_MONOTONIC in dhclient"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283256] CLOCK_MONOTONIC in dhclient"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283256] CLOCK_MONOTONIC in dhclient"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283256] CLOCK_MONOTONIC in dhclient"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 11 Dec 2024 12:52:23 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283256
Bug ID: 283256
Summary: CLOCK_MONOTONIC in dhclient
Product: Base System
Version: 14.2-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: bugs@FreeBSD.org
Reporter: bag@zurbagan.org
dhclient uses clock_gettime(CLOCK_MONOTONIC...) to track lease validity.
But CLOCK_MONOTONIC doesn't guarantee any relationship with wall clock. For
example clock_monotic starts counting from zero on each reboot of my Freebsd
14.2 in proxmox venv.
#> cat dhclient.leases.vtnet2 | tail -4
renew 4 1970/1/1 22:10:57;
rebind 4 1970/1/1 22:10:52;
expire 4 1970/1/1 22:11:57;
}
Because of this, saved leases (/var/db/dhclient.leases*) are incorrectly
considered usable as backup after a reboot.
--
You are receiving this mail because:
You are the assignee for the bug.