summaryrefslogtreecommitdiff
path: root/man/sd_journal_print.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2018-08-03 16:43:30 +0200
committerLennart Poettering <lennart@poettering.net>2018-08-03 17:36:11 +0200
commit64a7ef8bc06b5dcfcd9f99ea10a43bde75c4370f (patch)
treeab5905268e9686f76a5e9d35cd1352353bdfb8bc /man/sd_journal_print.xml
parentaf560fc1da26a7d0e94b0d56a3cd2a14d2b082c8 (diff)
downloadsystemd-64a7ef8bc06b5dcfcd9f99ea10a43bde75c4370f.tar.gz
man: be more explicit about thread safety of sd_journal
Triggered by https://bugzilla.redhat.com/show_bug.cgi?id=1609349 This adds two generic paragaphs we include via xinclude. One is the "strict" version, which contains wording saying that we are thread agnostic and what that means. And the other is the "safe" version, for the cases we provide fully safety. Let's then change most man pages to use either of these generic paragraphs. With one exception: man/sd_journal_get_catalog.xml contains both kinds of function, we hence use manual wording.
Diffstat (limited to 'man/sd_journal_print.xml')
-rw-r--r--man/sd_journal_print.xml3
1 files changed, 2 insertions, 1 deletions
diff --git a/man/sd_journal_print.xml b/man/sd_journal_print.xml
index f8ff7ba093..e18cf88bbc 100644
--- a/man/sd_journal_print.xml
+++ b/man/sd_journal_print.xml
@@ -177,7 +177,8 @@ sd_journal_send("MESSAGE=Hello World, this is PID %lu!", (unsigned long) getpid(
<refsect1>
<title>Thread safety</title>
- <para>All functions listed here are thread-safe and may be called in parallel from multiple threads.</para>
+
+ <xi:include href="threads-aware.xml" xpointer="safe"/>
<para><function>sd_journal_sendv()</function> is "async signal safe" in the meaning of <citerefentry
project='man-pages'><refentrytitle>signal-safety</refentrytitle><manvolnum>7</manvolnum></citerefentry>.