X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsd_journal_open.xml;h=76b857b9916e7a0faf194d4a47f067a02701d2b8;hb=886a64fe6903bc1ccde5c7af0eac6786918c8e49;hp=12b80551a273b8bc793b3cba4dc23874bb82c0e2;hpb=67c3cf4f9ea35c1f789526b24a4d052d071902c0;p=elogind.git
diff --git a/man/sd_journal_open.xml b/man/sd_journal_open.xml
index 12b80551a..76b857b99 100644
--- a/man/sd_journal_open.xml
+++ b/man/sd_journal_open.xml
@@ -46,6 +46,10 @@
sd_journal_open
sd_journal_open_directory
sd_journal_close
+ sd_journal
+ SD_JOURNAL_LOCAL_ONLY
+ SD_JOURNAL_RUNTIME_ONLY
+ SD_JOURNAL_SYSTEM_ONLY
Open the system journal for reading
@@ -67,7 +71,7 @@
- int sd_journal_close
+ void sd_journal_close
sd_journal* j
@@ -76,19 +80,19 @@
Description
- sd_journal_open() opens the
+ sd_journal_open() opens
the log journal for reading. It will find all journal
files automatically and interleave them automatically
when reading. As first argument it takes a pointer to
a sd_journal pointer, which on
- success will contain journal context afterwards. The
+ success will contain journal context object afterwards. The
second argument is a flags field, which may consist of
the following flags ORed together:
SD_JOURNAL_LOCAL_ONLY makes sure
only journal files generated on the local machine will
be opened. SD_JOURNAL_RUNTIME_ONLY
makes sure only volatile journal files will be opened,
- excluding those which are stored on persistant
+ excluding those which are stored on persistent
storage. SD_JOURNAL_SYSTEM_ONLY
will ensure that only journal files of system services
and the kernel (in opposition to user session processes) will
@@ -116,8 +120,31 @@
See
sd_journal_next3
for an example how to iterate through the journal
- after opening it it with
+ after opening it with
sd_journal_open().
+
+ A journal context object returned by
+ sd_journal_open() references a
+ specific journal entry as current entry,
+ similar to a file seek index in a classic file system
+ file, but without absolute positions. It may be
+ altered with
+ sd_journal_next3
+ and
+ sd_journal_seek_head3
+ and related calls. The current entry position may be
+ exported in cursor strings, as accessible
+ via
+ sd_journal_get_cursor3. Cursor
+ strings may be used to globally identify a specific
+ journal entry in a stable way and then later to seek
+ to it (or if the specific entry is not available
+ locally, to its closest entry in time)
+ sd_journal_seek_cursor3.
+
+ Notification of journal changes is available via
+ sd_journal_get_fd() and related
+ calls.