diff options
Diffstat (limited to 'chapter07/usage.xml')
| -rw-r--r-- | chapter07/usage.xml | 72 |
1 files changed, 42 insertions, 30 deletions
diff --git a/chapter07/usage.xml b/chapter07/usage.xml index 6fedb31d9..686d4be7d 100644 --- a/chapter07/usage.xml +++ b/chapter07/usage.xml @@ -21,7 +21,7 @@ accepted standards.</para> <para>SysVinit (which we'll call <emphasis>init</emphasis> from now on) works using a run-levels scheme. There are 7 (from 0 to 6) run-levels (actually, there are more run-levels but they are for special cases and -generally not used. The init man page describes those details), and each +generally not used. The <command>init</command> man page describes those details), and each one of those corresponds to the things the computer is supposed to do when it starts up. The default run-level is 3. Here are the descriptions of the different run-levels as they are often implemented:</para> @@ -36,13 +36,14 @@ different run-levels as they are often implemented:</para> <para>The command used to change run-levels is <command>init <runlevel></command> where <runlevel> is the target run-level. For -example, to reboot the computer, a user would issue the <command>init -6</command> command. The <command>reboot</command> command is just an alias for +example, to reboot the computer, a user would issue the <userinput>init +6</userinput> command. The <command>reboot</command> command is just an alias for it, as is the <command>halt</command> command an alias for <command>init 0</command>.</para> -<para>There are a number of directories under <filename>/etc/rc.d</filename> -that look like like rc?.d (where ? is the number of the run-level) and rcsysinit.d +<para>There are a number of directories under <filename class="directory">/etc/rc.d</filename> +that look like like <filename class="directory">rc?.d</filename> (where ? is the +number of the run-level) and <filename class="directory">rcsysinit.d</filename> all containing a number of symbolic links. Some begin with a K, the others begin with an S, and all of them have two numbers following the initial letter. The K means to stop (kill) a service, and the S means to start a service. The numbers @@ -50,17 +51,20 @@ determine the order in which the scripts are run, from 00 to 99; the lower the number the sooner it gets executed. When init switches to another run-level, the appropriate services get killed and others get started.</para> -<para>The real scripts are in /etc/rc.d/init.d. They do all the work, and the -symlinks all point to them. Killing links and starting links point to -the same script in /etc/rc.d/init.d. That's because the scripts can be -called with different parameters like start, stop, restart, reload, -status. When a K link is encountered, the appropriate script is run with -the stop argument. When an S link is encountered, the appropriate script -is run with the start argument.</para> +<para>The real scripts are in <filename class="directory">/etc/rc.d/init.d</filename>. +They do all the work, and the symlinks all point to them. Killing links and starting links +point to the same script in <filename class="directory">/etc/rc.d/init.d</filename>. +That's because the scripts can be called with different parameters like +<parameter>start</parameter>, <parameter>stop</parameter>, +<parameter>restart</parameter>, <parameter>reload</parameter>, +<parameter>status</parameter>. When a K link is encountered, the appropriate +script is run with the <parameter>stop</parameter> argument. When an S link is +encountered, the appropriate script is run with the <parameter>start</parameter> +argument.</para> <para>There is one exception. Links that start with an S in the rc0.d and rc6.d directories will not cause anything to be started. They -will be called with the parameter <emphasis>stop</emphasis> to stop +will be called with the parameter <parameter>stop</parameter> to stop something. The logic behind it is that when you are going to reboot or halt the system, you don't want to start anything, only stop the system.</para> @@ -68,26 +72,34 @@ system.</para> <para>These are descriptions of what the arguments make the scripts do:</para> -<itemizedlist> - -<listitem><para><emphasis>start</emphasis>: The service is -started.</para></listitem> - -<listitem><para><emphasis>stop</emphasis>: The service is -stopped.</para></listitem> - -<listitem><para><emphasis>restart</emphasis>: The service is -stopped and then started again.</para></listitem> - -<listitem><para><emphasis>reload</emphasis>: The configuration -of the service is updated. +<variablelist> +<varlistentry> +<term><parameter>start</parameter></term> +<listitem><para>The service is started.</para></listitem> +</varlistentry> + +<varlistentry> +<term><parameter>stop</parameter></term> +<listitem><para>The service is stopped.</para></listitem> +</varlistentry> + +<varlistentry> +<term><parameter>restart</parameter></term> +<listitem><para>The service is stopped and then started again.</para></listitem> +</varlistentry> + +<varlistentry> +<term><parameter>reload</parameter></term> +<listitem><para>The configuration of the service is updated. This is used after the configuration file of a service was modified, when the service doesn't need to be restarted.</para></listitem> +</varlistentry> -<listitem><para><emphasis>status</emphasis>: Tells if the service -is running and with which PIDs.</para></listitem> - -</itemizedlist> +<varlistentry> +<term><parameter>status</parameter></term> +<listitem><para>Tells if the service is running and with which PIDs.</para></listitem> +</varlistentry> +</variablelist> <para>Feel free to modify the way the boot process works (after all, it's your own LFS system). The files given here are just an example of how it can be |