X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsd_journal_seek_head.xml;h=03de30a383c0570e763cf8c7f0f9bce0e87234b8;hp=b6a9a731c115a06ad8ab5321f0652e7026bcab18;hb=f24e86530ce0645e88022497af7d238f9c366946;hpb=639a6a2529dd5a3109b998ccb44fb75b97525e13 diff --git a/man/sd_journal_seek_head.xml b/man/sd_journal_seek_head.xml index b6a9a731c..03de30a38 100644 --- a/man/sd_journal_seek_head.xml +++ b/man/sd_journal_seek_head.xml @@ -92,7 +92,7 @@ sd_journal_seek_head() seeks to the beginning of the journal, i.e. the oldest - avilable entry. + available entry. Similar, sd_journal_seek_tail() may be @@ -101,36 +101,43 @@ sd_journal_seek_monotonic_usec() seeks to the entry with the specified monotonic - timestamp, i.e. CLOCK_MONOOTONIC. Since monotonic time - restarts on every reboot a boot ID needs to be - specified as well. + 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 - realtime timestamp is ambiguous it is not defined - which position is seeked to. + (wallclock) timestamp, + i.e. CLOCK_REALTIME. Note that + 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. + string. For details on cursors, see + 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 a separate step with a subsequent sd_journal_next3 - invocation (or a similar call). Only then entry data + invocation (or a similar call). Only then, entry data may be retrieved via sd_journal_get_data3. If no entry exists that matches exactly the specified - seek address the next closest is seeked to. If + seek address, the next closest is sought to. If sd_journal_next3 - is used the closest following entry will be seeked to, + is used, the closest following entry will be sought to, if sd_journal_previous3 - is used the closest preceeding entry is seeked + is used the closest preceding entry is sought to. @@ -151,8 +158,7 @@ and sd_journal_seek_cursor() interfaces are available as shared library, which can be compiled and linked to with the - libsystemd-journal - pkg-config1 + libsystemd-journal pkg-config1 file.