man.bsd.lv manual page server

Manual Page Search Parameters
NANOSLEEP(2) System Calls Manual NANOSLEEP(2)

nanosleep, clock_nanosleep — high resolution sleep

library “libc”

#include <time.h>

int
nanosleep(const struct timespec *rqtp, struct timespec *rmtp);

int
clock_nanosleep(clockid_t clock_id, int flags, const struct timespec *rqtp, struct timespec *rmtp);

Both () and clock_nanosleep() allow to suspend the calling thread for an interval measured in nanoseconds. Compared to nanosleep(), clock_nanosleep() further allows the caller to select the clock against which the suspension interval is to be measured, and allows the suspension interval to be specified as either a relative or an absolute value.

If the flags argument is 0 (i.e., the TIMER_ABSTIME flag is not set), the value specified in the rqtp argument is interpreted as an interval relative to the current time measured in the clock specified by the clock_id argument. Then () suspends execution of the calling thread until either the time interval specified by the rqtp argument has elapsed, or a signal is delivered to the calling process and its action is to invoke a signal-catching function or to terminate the process.

If the flags argument is TIMER_ABSTIME, the value specified in the rqtp argument is interpreted as an absolute time measured by the clock_id clock. Then () suspends execution of the calling thread until either the value of the clock specified by the clock_id argument reaches the absolute time specified by the rqtp argument, or a signal is delivered to the calling process and its action is to invoke a signal-catching function or to terminate the process. If, at the time of the call, the time value specified by rqtp is less than or equal to the time value of the specified clock, then clock_nanosleep() returns immediately and the calling thread is not suspended.

The suspension time may be longer than requested due to the scheduling of other activity by the system. An unmasked signal will terminate the sleep early, regardless of the SA_RESTART value on the interrupting signal. The rqtp and rmtp arguments can point to the same object.

The following clock_id values (see clock_gettime(2) for their meanings) are supported:

The () function behaves like clock_nanosleep() with a clock_id argument of CLOCK_REALTIME and without the TIMER_ABSTIME flag in the flags argument.

The use of these functions has no effect on the action or blockage of any signal.

These functions return zero when the requested time has elapsed.

If these functions return for any other reason, then clock_nanosleep() will directly return the error number, and nanosleep() will return -1 with the global variable errno set to indicate the error. If a relative sleep is interrupted by a signal and rmtp is non-NULL, the timespec structure it references is updated to contain the unslept amount (the request time minus the time actually slept).

These functions can fail with the following errors:

[]
Either rqtp or rmtp points to memory that is not a valid part of the process address space.
[]
The function was interrupted by the delivery of a signal.
[]
The rqtp argument specified a nanosecond value less than zero or greater than or equal to 1000 million.
[]
The flags argument contained an invalid flag.
[]
The clock_id argument was CLOCK_THREAD_CPUTIME_ID or an unrecognized value.
[]
The clock_id argument was valid but not supported by this implementation of clock_nanosleep().

clock_gettime(2), sigaction(2), sleep(3)

The nanosleep() function conforms to IEEE Std 1003.1b-1993 (“POSIX.1b”). The clock_nanosleep() function conforms to IEEE Std 1003.1-2008 (“POSIX.1”).

January 17, 2021 DragonFly-6.0.1