2014-11-28 01:13:12 +03:00
<?xml version="1.0"?>
<!-- * - nxml - * -->
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2014-11-28 01:13:12 +03:00
<refentry id= "systemd-sysv-generator" conditional= "HAVE_SYSV_COMPAT" >
<refentryinfo >
<title > systemd-sysv-generator</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-sysv-generator</refentrytitle>
<manvolnum > 8</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-sysv-generator</refname>
<refpurpose > Unit generator for SysV init scripts</refpurpose>
</refnamediv>
<refsynopsisdiv >
2015-06-18 20:47:44 +03:00
<para > <filename > /usr/lib/systemd/system-generators/systemd-sysv-generator</filename> </para>
2014-11-28 01:13:12 +03:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <filename > systemd-sysv-generator</filename> is a generator
that creates wrapper .service units for
<ulink url= "https://savannah.nongnu.org/projects/sysvinit" > SysV init</ulink>
scripts in <filename > /etc/init.d/*</filename> at boot and when
2021-09-27 09:43:10 +03:00
configuration of the system manager is reloaded. This allows
2014-11-28 01:13:12 +03:00
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
to support them similarly to native units.</para>
<para > <ulink url= "http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html" > LSB headers</ulink>
in SysV init scripts are interpreted, and the ordering specified
in the header is turned into dependencies between the generated
2014-08-03 09:11:37 +04:00
unit and other units. The LSB facilities
2014-11-28 01:13:12 +03:00
<literal > $remote_fs</literal> , <literal > $network</literal> ,
<literal > $named</literal> , <literal > $portmap</literal> ,
<literal > $time</literal> are supported and will be turned into
dependencies on specific native systemd targets. See
2020-07-11 01:05:23 +03:00
<citerefentry > <refentrytitle > systemd.special</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
2014-11-28 01:13:12 +03:00
for more details.</para>
2021-09-27 09:43:10 +03:00
<para > Note that compatibility is quite comprehensive but not 100%, for more details see <ulink
url="https://www.freedesktop.org/wiki/Software/systemd/Incompatibilities">Incompatibilities with
SysV</ulink> .</para>
2014-11-28 01:13:12 +03:00
<para > SysV runlevels have corresponding systemd targets
(<filename > runlevel<replaceable > X</replaceable> .target</filename> ).
2014-08-03 09:11:37 +04:00
The wrapper unit that is generated will be wanted by those targets
2014-11-28 01:13:12 +03:00
which correspond to runlevels for which the script is
enabled.</para>
2016-03-20 04:24:30 +03:00
<para > <command > systemd</command> does not support SysV scripts as
2014-11-28 01:13:12 +03:00
part of early boot, so all wrapper units are ordered after
<filename > basic.target</filename> .</para>
2015-03-05 02:43:20 +03:00
<para > <filename > systemd-sysv-generator</filename> implements
<citerefentry > <refentrytitle > systemd.generator</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> .</para>
2014-11-28 01:13:12 +03:00
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.target</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
</para>
</refsect1>
</refentry>