]> git.ipfire.org Git - thirdparty/systemd.git/blob - man/systemd-sysv-generator.xml
core: introduce new Type=exec service type
[thirdparty/systemd.git] / man / systemd-sysv-generator.xml
1 <?xml version="1.0"?>
2 <!--*-nxml-*-->
3 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
4 <!--
5 SPDX-License-Identifier: LGPL-2.1+
6 -->
7 <refentry id="systemd-sysv-generator" conditional="HAVE_SYSV_COMPAT">
8
9 <refentryinfo>
10 <title>systemd-sysv-generator</title>
11 <productname>systemd</productname>
12 </refentryinfo>
13
14 <refmeta>
15 <refentrytitle>systemd-sysv-generator</refentrytitle>
16 <manvolnum>8</manvolnum>
17 </refmeta>
18
19 <refnamediv>
20 <refname>systemd-sysv-generator</refname>
21 <refpurpose>Unit generator for SysV init scripts</refpurpose>
22 </refnamediv>
23
24 <refsynopsisdiv>
25 <para><filename>/usr/lib/systemd/system-generators/systemd-sysv-generator</filename></para>
26 </refsynopsisdiv>
27
28 <refsect1>
29 <title>Description</title>
30
31 <para><filename>systemd-sysv-generator</filename> is a generator
32 that creates wrapper .service units for
33 <ulink url="https://savannah.nongnu.org/projects/sysvinit">SysV init</ulink>
34 scripts in <filename>/etc/init.d/*</filename> at boot and when
35 configuration of the system manager is reloaded. This will allow
36 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
37 to support them similarly to native units.</para>
38
39 <para><ulink url="http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html">LSB headers</ulink>
40 in SysV init scripts are interpreted, and the ordering specified
41 in the header is turned into dependencies between the generated
42 unit and other units. The LSB facilities
43 <literal>$remote_fs</literal>, <literal>$network</literal>,
44 <literal>$named</literal>, <literal>$portmap</literal>,
45 <literal>$time</literal> are supported and will be turned into
46 dependencies on specific native systemd targets. See
47 <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>5</manvolnum></citerefentry>
48 for more details.</para>
49
50 <para>SysV runlevels have corresponding systemd targets
51 (<filename>runlevel<replaceable>X</replaceable>.target</filename>).
52 The wrapper unit that is generated will be wanted by those targets
53 which correspond to runlevels for which the script is
54 enabled.</para>
55
56 <para><command>systemd</command> does not support SysV scripts as
57 part of early boot, so all wrapper units are ordered after
58 <filename>basic.target</filename>.</para>
59
60 <para><filename>systemd-sysv-generator</filename> implements
61 <citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
62 </refsect1>
63
64 <refsect1>
65 <title>See Also</title>
66 <para>
67 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
68 <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
69 <citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>
70 </para>
71 </refsect1>
72
73 </refentry>