From b59866aefa110d368460edc14f98cd6d79fe05cd Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 13 Jul 2012 20:17:37 +0200 Subject: man: document sd_journal_get_cutoff_realtime_usec() --- man/sd_journal_get_realtime_usec.xml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'man/sd_journal_get_realtime_usec.xml') diff --git a/man/sd_journal_get_realtime_usec.xml b/man/sd_journal_get_realtime_usec.xml index bebf4f5a3c..a8aa3a4772 100644 --- a/man/sd_journal_get_realtime_usec.xml +++ b/man/sd_journal_get_realtime_usec.xml @@ -72,15 +72,15 @@ Description sd_journal_get_realtime_usec() - gets the realtime (wallclock) timestamp of the the + gets the realtime (wallclock) timestamp of the current journal entry. It takes two arguments: the journal context object and a pointer to a 64 Bit unsigned integer to store the timestamp in. The timestamp is in microseconds since the epoch, i.e. CLOCK_REALTIME. - sd_journal_get_realtime_usec() - gets the monotonic timestamp of the the current + sd_journal_get_monotonic_usec() + gets the monotonic timestamp of the current journal entry. It takes three arguments: the journal context object, a pointer to a 64 Bit unsigned integer to store the timestamp in as well as a 128 Bit ID @@ -89,7 +89,7 @@ the specific boot, i.e. CLOCK_MONOTONIC. Since the monotonic clock begins new with every reboot it only defines a well-defined point in time when used - together with a identifier identifying the boot, see + together with an identifier identifying the boot, see sd_id128_get_boot3 for more information. If the boot ID parameter is passed NULL the function will fail if the monotonic @@ -138,7 +138,8 @@ sd_journal_next3, sd_journal_get_data3, sd_id128_get_boot3, - clock_gettime2 + clock_gettime2, + sd_journal_get_cutoff_realtime_usec3 -- cgit v1.2.3-54-g00ecf