X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsd_journal_get_realtime_usec.xml;h=515932c6d89fcdf4d8d0ceff4a20d725d1b94a72;hb=735e0712710a1dc26da0febafb91b242b2687f3f;hp=bebf4f5a3ce1a2dde1d911c04f2576d377465935;hpb=7a8a6e88545bf22909941c9b022873709a1a1c9e;p=elogind.git
diff --git a/man/sd_journal_get_realtime_usec.xml b/man/sd_journal_get_realtime_usec.xml
index bebf4f5a3..515932c6d 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
@@ -99,7 +99,7 @@
Note that these functions will not work before
sd_journal_next3
(or related call) has been called at least
- once.
+ once, in order to position the read pointer at a valid entry.
@@ -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