can be rotated at any moment, and the opening of
specific files is inherently racy.</para>
+ <para><varname>sd_journal</varname> objects cannot be
+ used in the child after a fork. Functions which take a
+ journal object as an argument
+ (<function>sd_journal_next()</function> and others)
+ will return <constant>-ECHILD</constant> after a fork.
+ </para>
+
<para><function>sd_journal_close()</function> will
close the journal context allocated with
<function>sd_journal_open()</function> or
<para>When opening the journal only journal files
accessible to the calling user will be opened. If
- journal files are not accessible to the caller this
+ journal files are not accessible to the caller, this
will be silently ignored.</para>
<para>See
<function>sd_journal_close()</function> interfaces are
available as a shared library, which can be compiled and
linked to with the
- <constant>libsystemd-journal</constant>
- <citerefentry><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+ <constant>libsystemd-journal</constant> <citerefentry><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry>
file.</para>
</refsect1>