LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

timerfd_create.2: Rework discussion on relative and absolute timers 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-11-21 15:46:52 +01:00
parent 4c7471193b
commit 510625764c
1 changed files with 21 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
man2/timerfd_create.2
View File

@ -186,22 +186,30 @@ If both fields of
are zero, the timer expires just once, at the time specified by
.IR new_value.it_value .
By default,
the initial expiration time specified in
.I new_value
is interpreted relative to the current time
on the timer's clock at the time of the call (i.e.,
.I new_value.it_value
specifies a time relative to the current value of the clock specified by
.IR clockid ).
An absolute timeout can be selected via the
.I flags
argument.
The
.I flags
argument is either 0, to start a relative timer
.RI ( new_value.it_value
specifies a time relative to the current value of the clock specified by
.IR clockid ),
or
.BR TFD_TIMER_ABSTIME ,
to start an absolute timer
.RI ( new_value.it_value
specifies an absolute time for the clock specified by
.IR clockid ;
that is, the timer will expire when the value of that
argument is a bit mask that can include the following values:
.TP
.B TFD_TIMER_ABSTIME
Interpret
.I new_value.it_value
as an absolute value on the timer's clock.
The timer will expire when the value of the timer's
clock reaches the value specified in
.IR new_value.it_value ).
.IR new_value.it_value .
.PP
If the
.I old_value
argument is not NULL, then the