X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsd_journal_seek_head.xml;h=d24b2f30ee233dfdd9caf652abd8b19000ffa803;hb=97d0e5f83ba4dd713170f802b90149b7325bc992;hp=f8a4eb1d20bdc1b7b192692dfa55f63e47915b19;hpb=49f43d5f91a99b23f745726aa351d8f159774357;p=elogind.git
diff --git a/man/sd_journal_seek_head.xml b/man/sd_journal_seek_head.xml
index f8a4eb1d2..d24b2f30e 100644
--- a/man/sd_journal_seek_head.xml
+++ b/man/sd_journal_seek_head.xml
@@ -101,21 +101,26 @@
sd_journal_seek_monotonic_usec()
seeks to the entry with the specified monotonic
- timestamp, i.e. CLOCK_MONOOTONIC. Since monotonic time
+ timestamp, i.e. CLOCK_MONOTONIC. Since monotonic time
restarts on every reboot a boot ID needs to be
specified as well.
sd_journal_seek_realtime_usec()
seeks to the entry with the specified realtime
(wallclock) timestamp, i.e. CLOCK_REALTIME. Note that
- the realtime clock is not necessary monotonic. If a
+ the realtime clock is not necessarily monotonic. If a
realtime timestamp is ambiguous it is not defined
which position is sought to.
sd_journal_seek_cursor()
seeks to the entry located at the specified cursor
string. For details on cursors see
- sd_journal_get_cursor3.
+ sd_journal_get_cursor3. If
+ no entry matching the specified cursor is found the
+ call will seek to the next closest entry (in terms of
+ time) instead. To verify whether the newly selected
+ entry actually matches the cursor use
+ sd_journal_test_cursor3.
Note that these calls do not actually make any
entry the new current entry, this needs to be done in