Messages in this thread | | | Date | Tue, 24 Jun 2008 11:27:33 +0200 | From | "Bart Van Assche" <> | Subject | Re: nanosleep() uses CLOCK_MONOTONIC, should be CLOCK_REALTIME? |
| |
>> nor by adjtimex() (this last one is used by ntpd). > > That surprised me a little. So gradual adjustments to the time made > by adjtime() / adjtimex() really don't affect nanosleep()?
Does the adjtime() system call still exist ? I could not find any information about this system call in the 2.6.25 kernel source code.
Frequency adjustments made via the adjtimex() system call do affect nanosleep() of course (via timex::freq and/or timex::tick). Stepwise time adjustments, whether gradual or not, should not affect nanosleep().
Bart.
| |