summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
Diffstat (limited to 'man')
-rw-r--r--man/sd_notify.xml14
-rw-r--r--man/systemd.time.xml4
2 files changed, 14 insertions, 4 deletions
diff --git a/man/sd_notify.xml b/man/sd_notify.xml
index b82d145860..89f1729b13 100644
--- a/man/sd_notify.xml
+++ b/man/sd_notify.xml
@@ -24,6 +24,7 @@
<refname>sd_pid_notify_with_fds</refname>
<refname>sd_pid_notifyf_with_fds</refname>
<refname>sd_notify_barrier</refname>
+ <refname>sd_pid_notify_barrier</refname>
<refpurpose>Notify service manager about start-up completion and other service status changes</refpurpose>
</refnamediv>
@@ -83,6 +84,13 @@
<paramdef>int <parameter>unset_environment</parameter></paramdef>
<paramdef>uint64_t <parameter>timeout</parameter></paramdef>
</funcprototype>
+
+ <funcprototype>
+ <funcdef>int <function>sd_pid_notify_barrier</function></funcdef>
+ <paramdef>pid_t <parameter>pid</parameter></paramdef>
+ <paramdef>int <parameter>unset_environment</parameter></paramdef>
+ <paramdef>uint64_t <parameter>timeout</parameter></paramdef>
+ </funcprototype>
</funcsynopsis>
</refsynopsisdiv>
@@ -372,8 +380,10 @@
previously sent notification messages and uses the <varname>BARRIER=1</varname> command. It takes a
relative <varname>timeout</varname> value in microseconds which is passed to
<citerefentry><refentrytitle>ppoll</refentrytitle><manvolnum>2</manvolnum>
- </citerefentry>. A value of UINT64_MAX is interpreted as infinite timeout.
- </para>
+ </citerefentry>. A value of UINT64_MAX is interpreted as infinite timeout.</para>
+
+ <para><function>sd_pid_notify_barrier()</function> is just like <function>sd_notify_barrier()</function>,
+ but allows specifying the originating PID for the notification message.</para>
</refsect1>
<refsect1>
diff --git a/man/systemd.time.xml b/man/systemd.time.xml
index 643ff7d78f..07100b12b7 100644
--- a/man/systemd.time.xml
+++ b/man/systemd.time.xml
@@ -229,8 +229,8 @@ tomorrow Pacific/Auckland → Thu 2012-11-23 19:00:00
decimal places.</para>
<para>Either time or date specification may be omitted, in which
- case the current day and 00:00:00 is implied, respectively. If the
- second component is not specified, <literal>:00</literal> is
+ case *-*-* and 00:00:00 is implied, respectively. If the
+ seconds component is not specified, <literal>:00</literal> is
assumed.</para>
<para>Timezone can be specified as the literal string <literal>UTC</literal>, or