tags + upstream thanks Hi,
On Mon, Aug 10, 2009 at 11:30:34AM -0700, Josh Triplett wrote: > Package: manpages > Version: 3.22-1 > Severity: wishlist > > Developers of real-time programs (programs using real-time scheduling > and/or expecting low latency) sometimes see CLOCK_REALTIME and think > they want to use that, when they almost certainly don't. Please > consider adding some clarification that the "real-time" of > CLOCK_REALTIME refers to wall-clock time (as opposed to CPU or process > time, for instance) and that developers of real-time applications want > to use CLOCK_MONOTONIC. Michael Kerrisk improved clock_getres.2 in manpages 3.40: .B CLOCK_MONOTONIC Clock that cannot be set and represents monotonic time since some unspecified starting point. +This clock is not affected by discontinuous jumps in the system time +(e.g., if the system administrator manually changes the clock), +but is affected by the incremental adjustments performed by +.BR adjtime (2) +and NTP. Maybe one can add (please proofread my english): "This clock allow to precisely measuring time elapsed, for use in real-time programs." http://pubs.opengroup.org/onlinepubs/009604599/functions/clock_getres.html -- Simon Paillard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
