bump
On Mon, 18 Oct 2021 at 23:47, zack leung wrote:
> bump
>
>
> On Wed, 6 Oct 2021 at 00:30, zack leung wrote:
>
>> For relative times, the clock identifier is not used to select the clock
>> and instead always the CLOCK_MONOTONIC is used. A side-effect is that
>> sleep() and nanosleep() use
bump
On Wed, 6 Oct 2021 at 00:30, zack leung wrote:
> For relative times, the clock identifier is not used to select the clock
> and instead always the CLOCK_MONOTONIC is used. A side-effect is that
> sleep() and nanosleep() use the wrong clock (CLOCK_MONOTONIC instead of
> CLOCK_REALTIME).
>
>
For relative times, the clock identifier is not used to select the clock
and instead always the CLOCK_MONOTONIC is used. A side-effect is that
sleep() and nanosleep() use the wrong clock (CLOCK_MONOTONIC instead of
CLOCK_REALTIME).
I don't understand how the monotonic clock is not being used. I kn
