picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

man: add various links from man pages to appropriate wiki pages

This commit is contained in:
Lennart Poettering 2012-06-28 18:58:56 +02:00
parent 305f376cec
commit 9980033377
6 changed files with 37 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
man/systemctl.xml
View File

@ -821,8 +821,12 @@
<command>enable</command>, depending
how the unit is listed in the preset
files. For more information on preset
policy see
<citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
policy format see
<citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
more information on the concept of
presets please consult the <ulink
url="http://freedesktop.org/wiki/Software/systemd/Preset">Preset</ulink>
document.</para>
</listitem>
</varlistentry>

5
man/systemd-nspawn.xml
View File

@ -114,6 +114,11 @@
two containers is complete and the containers will
share very few runtime objects except for the
underlying file system.</para>
<para><command>systemd-nspawn</command> implements the
<ulink
url="http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">Container
Interface</ulink> specification.</para>
</refsect1>
<refsect1>

5
man/systemd.preset.xml
View File

@ -72,6 +72,11 @@
set of units to be enabled/disabled even before
installing the actual package.</para>
<para>For more information on the preset logic please
have a look at the <ulink
url="http://freedesktop.org/wiki/Software/systemd/Preset">Presets</ulink>
document.</para>
<para>It is not recommended to ship preset files
within the respective software packages implementing
the units, but rather centralize them in a

7
man/systemd.service.xml
View File

@ -95,7 +95,12 @@
<filename>.service</filename> suffix removed) and
dynamically creates a service unit from that
script. This is useful for compatibility with
SysV.</para>
SysV. Note that this compatibility is quite
comprehensive but not 100%. For details about the
incomptibilities see the <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities">Incompatibilities
with SysV</ulink> document.
</para>
</refsect1>
<refsect1>

21
man/systemd.special.xml
View File

@ -93,7 +93,6 @@
<filename>suspend.target</filename>,
<filename>swap.target</filename>,
<filename>sysinit.target</filename>,
<filename>syslog.service</filename>,
<filename>syslog.socket</filename>,
<filename>syslog.target</filename>,
<filename>system-update.target</filename>,
@ -730,17 +729,6 @@
or b.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>syslog.service</filename></term>
<listitem>
<para>The syslog service if
any. Implementations should
create a symlink from the
actual syslog implementation
to this generic name for
activating it.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>syslog.socket</filename></term>
<listitem>
@ -748,8 +736,13 @@
syslog implementations should
listen on. All userspace log
messages will be made
available on this
socket.</para>
available on this socket. For
more information about syslog
integration, please consult
the <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/syslog">Syslog
Interface</ulink>
document.</para>
</listitem>
</varlistentry>
<varlistentry>

8
man/systemd.xml
View File

@ -487,6 +487,14 @@
command line. For details see the <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/Generators">Generators
Specification</ulink>.</para>
<para>Systems which invoke systemd in a container
resp. initrd environment should implement the
<ulink
url="http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">Container
Interface</ulink> resp. <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/InitrdInterface">initrd
Interface</ulink> specifications.</para>
</refsect1>
<refsect1>