man/systemd-sysv-generator.xml

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