-
Notifications
You must be signed in to change notification settings - Fork 167
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
Please support CLOCK_BOOTTIME
in clock_gettime
on Linux
#905
Comments
Thanks for the report! Rustix's current (and currently undocumented) policy has been to support Linux 2.6.32, but it does seem to make sense to change that, and document it. I filed #907 to propose this and collect feedback. In the meantime, adding |
#911 will add |
rustix::time::ClockId
contains the clock IDs that always work, so thatclock_gettime
can't return an error. This enum already varies by platform, with some values only available oncfg(linux_kernel)
, and some values only available onnot(cfg(apple))
for instance.CLOCK_BOOTTIME
is available on a variety of platforms, including Linux 2.6.39 and newer. Even Debian oldoldstable has a 4.19 kernel. RHEL 7 is ten years old and uses a 3.10 kernel.If those aren't sufficient, then could you please:
linux_4_11
feature flag, andThank you!
The text was updated successfully, but these errors were encountered: