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=2ef37e528850adba69b7017fc80cac5501bc533c;hp=3716c5d3676f32d83cfcb63b074385e0fc42e38a;hb=a2e0337875addaf08225fbf9b231435ba12a88b5;hpb=f274ece0f76b5709408821e317e87aef76123db6 diff --git a/man/sd_journal_seek_head.xml b/man/sd_journal_seek_head.xml index 3716c5d36..2ef37e528 100644 --- a/man/sd_journal_seek_head.xml +++ b/man/sd_journal_seek_head.xml @@ -58,31 +58,31 @@ int sd_journal_seek_head - sd_journal* j + sd_journal *j int sd_journal_seek_tail - sd_journal* j + sd_journal *j int sd_journal_seek_monotonic_usec - sd_journal* j + sd_journal *j sd_id128_t boot_id uint64_t usec int sd_journal_seek_realtime_usec - sd_journal* j + sd_journal *j uint64_t usec int sd_journal_seek_cursor - sd_journal* j - const char * cursor + sd_journal *j + const char *cursor @@ -94,45 +94,47 @@ seeks to the beginning of the journal, i.e. the oldest available entry. - Similar, + Similarly, sd_journal_seek_tail() may be used to seek to the end of the journal, i.e. the most recent available entry. 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 + (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 + 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 + 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 + 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 sought to. If + seek address, the next closest is sought to. If sd_journal_next3 - is used the closest following entry will be sought to, + is used, the closest following entry will be sought to, if sd_journal_previous3 is used the closest preceding entry is sought @@ -154,10 +156,9 @@ sd_journal_seek_monotonic_usec(), sd_journal_seek_realtime_usec(), and sd_journal_seek_cursor() - interfaces are available as shared library, which can + interfaces are available as a shared library, which can be compiled and linked to with the - libsystemd-journal - pkg-config1 + libsystemd pkg-config1 file.