communication channels are established already, and no
request is lost because client requests will be queued
by the bus system (in case of D-Bus) or the kernel (in
- case of sockets), until the activation
+ case of sockets), until the activation is
completed.</para>
<refsect2>
install their systemd unit files in the
directory returned by <command>pkg-config
systemd
- --variable=systemdsystemnunitdir</command>
+ --variable=systemdsystemunitdir</command>
(for system services),
resp. <command>pkg-config systemd
--variable=systemdsessionunitdir</command>
package managers:</para>
<programlisting>%post
-/usr/bin/systemd-install enable foobar.service foobar.socket >/dev/null 2>&1 || :
+/usr/bin/systemd-install --realize enable foobar.service foobar.socket >/dev/null 2>&1 || :
%preun
if [ "$1" -eq 0 ]; then
- /usr/bin/systemd-install disable foobar.service foobar.socket >/dev/null 2>&1 || :
+ /usr/bin/systemd-install --realize disable foobar.service foobar.socket >/dev/null 2>&1 || :
fi</programlisting>
</refsect2>
<para>Since new-style init systems such as systemd are
compatible with traditional SysV init systems it is
not strictly necessary to port existing daemons to the
- new style. However doing this offers additional
- functionality to the daemons as well as it simplifies
+ new style. However doing so offers additional
+ functionality to the daemons as well as simplifying
integration into new-style init systems.</para>
<para>To port an existing SysV compatible daemon the
left-over file descriptors are passed to
executed processes, it might be a good choice
to simply skip the closing of all remaining
- open file descriptors if file descriptors are
+ open file descriptors if sockets are
passed.</para></listitem>
<listitem><para>Write and install a systemd