From: Lennart Poettering Date: Mon, 14 Apr 2014 00:42:11 +0000 (-0700) Subject: man: explain that the timestamps on incoming kdbus messages are not necessarily monot... X-Git-Tag: v213~413 X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=6e0369b0ff3909baec25c6ab31b5ddf5c4ae0f3f;ds=sidebyside man: explain that the timestamps on incoming kdbus messages are not necessarily monotonically increasing --- diff --git a/man/sd_bus_message_get_monotonic_usec.xml b/man/sd_bus_message_get_monotonic_usec.xml index 683931c4d..0a11a3123 100644 --- a/man/sd_bus_message_get_monotonic_usec.xml +++ b/man/sd_bus_message_get_monotonic_usec.xml @@ -92,9 +92,10 @@ sd_bus_message_get_seqnum() returns the kernel-assigned sequence number of the - message. The kernel assigns a global monotonically increasing - sequence number to all messages sent on the local - system. This sequence number is useful for determining + message. The kernel assigns a global, monotonically + increasing sequence number to all messages transmitted + on the local system, at the time the message was + sent. This sequence number is useful for determining message send order, even across different busses of the local system. The sequence number combined with the boot ID of the system (as returned by @@ -102,6 +103,12 @@ is a suitable globally unique identifier for bus messages. + Note that the sending order and receiving order + of messages might differ, in particular for broadcast + messages. This means that the sequence number and the + timestamps of messages a client reads are not + necessarily monotonically increasing. + These timestamps and the sequence number are attached to each message by the kernel and cannot be manipulated by the sender.