Considering that user-space expects CLOCK_MONOTONIC not to account time during which system is suspended, explicitly document this behavior as ABI. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx> CC: Michael Kerrisk <mtk.manpages@xxxxxxxxx> CC: Thomas Gleixner <tglx@xxxxxxxxxxxxx> CC: John Stultz <john.stultz@xxxxxxxxxx> CC: Stephen Boyd <sboyd@xxxxxxxxxx> CC: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> --- man2/clock_getres.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man2/clock_getres.2 b/man2/clock_getres.2 index 0812d159a..ca5ca87c8 100644 --- a/man2/clock_getres.2 +++ b/man2/clock_getres.2 @@ -144,7 +144,7 @@ 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 (3) -and NTP. +and NTP. It does not include time during which the system is suspended. .TP .BR CLOCK_MONOTONIC_COARSE " (since Linux 2.6.32; Linux-specific)" .\" Added in commit da15cfdae03351c689736f8d142618592e3cebc3 -- 2.11.0 -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
