[install-guide: 11/18] purging out legacy init scripts info
Pete Travis
immanetize at fedoraproject.org
Fri Oct 26 05:51:48 UTC 2012
commit be8359e36e1e71388d297b632e93e420f770a6bd
Author: Pete Travis <immanetize at fedoraproject.org>
Date: Tue Sep 11 00:32:13 2012 -0600
purging out legacy init scripts info
en-US/Boot_Init_Shutdown.xml | 104 +-----------------------------------------
1 files changed, 1 insertions(+), 103 deletions(-)
---
diff --git a/en-US/Boot_Init_Shutdown.xml b/en-US/Boot_Init_Shutdown.xml
index f404b1b..ad4c01f 100644
--- a/en-US/Boot_Init_Shutdown.xml
+++ b/en-US/Boot_Init_Shutdown.xml
@@ -376,109 +376,7 @@ Let's look at the different types of units:
<para>
The function and usage of legacy init systems and their configuration files is outside of the scope of this document.
</para>
- <para>
- Next, the <command>init</command> command sets the source function library, <filename>/etc/rc.d/init.d/functions</filename>, for the system, which configures how to start, kill, and determine the PID of a program.
- </para>
- <para>
- The <command>init</command> program starts all of the background processes by looking in the appropriate <filename>rc</filename> directory for the runlevel specified as the default in <filename>/etc/inittab</filename>. The <filename>rc</filename> directories are numbered to correspond to the runlevel they represent. For instance, <filename>/etc/rc.d/rc5.d/</filename> is the directory for runlevel 5.
- </para>
- <para>
- When booting to runlevel 5, the <command>init</command> program looks in the <filename>/etc/rc.d/rc5.d/</filename> directory to determine which processes to start and stop.
- </para>
- <para>
- Below is an example listing of the <filename>/etc/rc.d/rc5.d/</filename> directory:
- </para>
-
-<screen>
-K05innd -> ../init.d/innd
-K05saslauthd -> ../init.d/saslauthd
-K10dc_server -> ../init.d/dc_server
-K10psacct -> ../init.d/psacct
-K10radiusd -> ../init.d/radiusd
-K12dc_client -> ../init.d/dc_client
-K12FreeWnn -> ../init.d/FreeWnn
-K12mailman -> ../init.d/mailman
-K12mysqld -> ../init.d/mysqld
-K15httpd -> ../init.d/httpd
-K20netdump-server -> ../init.d/netdump-server
-K20rstatd -> ../init.d/rstatd
-K20rusersd -> ../init.d/rusersd
-K20rwhod -> ../init.d/rwhod
-K24irda -> ../init.d/irda
-K25squid -> ../init.d/squid
-K28amd -> ../init.d/amd
-K30spamassassin -> ../init.d/spamassassin
-K34dhcrelay -> ../init.d/dhcrelay
-K34yppasswdd -> ../init.d/yppasswdd
-K35dhcpd -> ../init.d/dhcpd
-K35smb -> ../init.d/smb
-K35vncserver -> ../init.d/vncserver
-K36lisa -> ../init.d/lisa
-K45arpwatch -> ../init.d/arpwatch
-K45named -> ../init.d/named
-K46radvd -> ../init.d/radvd
-K50netdump -> ../init.d/netdump
-K50snmpd -> ../init.d/snmpd
-K50snmptrapd -> ../init.d/snmptrapd
-K50tux -> ../init.d/tux
-K50vsftpd -> ../init.d/vsftpd
-K54dovecot -> ../init.d/dovecot
-K61ldap -> ../init.d/ldap
-K65kadmin -> ../init.d/kadmin
-K65kprop -> ../init.d/kprop
-K65krb524 -> ../init.d/krb524
-K65krb5kdc -> ../init.d/krb5kdc
-K70aep1000 -> ../init.d/aep1000
-K70bcm5820 -> ../init.d/bcm5820
-K74ypserv -> ../init.d/ypserv
-K74ypxfrd -> ../init.d/ypxfrd
-K85mdmpd -> ../init.d/mdmpd
-K89netplugd -> ../init.d/netplugd
-K99microcode_ctl -> ../init.d/microcode_ctl
-S04readahead_early -> ../init.d/readahead_early
-S05kudzu -> ../init.d/kudzu
-S06cpuspeed -> ../init.d/cpuspeed
-S08ip6tables -> ../init.d/ip6tables
-S08iptables -> ../init.d/iptables
-S09isdn -> ../init.d/isdn
-S10network -> ../init.d/network
-S12syslog -> ../init.d/syslog
-S13irqbalance -> ../init.d/irqbalance
-S13portmap -> ../init.d/portmap
-S15mdmonitor -> ../init.d/mdmonitor
-S15zebra -> ../init.d/zebra
-S16bgpd -> ../init.d/bgpd
-S16ospf6d -> ../init.d/ospf6d
-S16ospfd -> ../init.d/ospfd
-S16ripd -> ../init.d/ripd
-S16ripngd -> ../init.d/ripngd
-S20random -> ../init.d/random
-S24pcmcia -> ../init.d/pcmcia
-S25netfs -> ../init.d/netfs
-S26apmd -> ../init.d/apmd
-S27ypbind -> ../init.d/ypbind
-S28autofs -> ../init.d/autofs
-S40smartd -> ../init.d/smartd
-S44acpid -> ../init.d/acpid
-S54hpoj -> ../init.d/hpoj
-S55cups -> ../init.d/cups
-S55sshd -> ../init.d/sshd
-S56rawdevices -> ../init.d/rawdevices
-S56xinetd -> ../init.d/xinetd
-S58ntpd -> ../init.d/ntpd
-S75postgresql -> ../init.d/postgresql
-S80sendmail -> ../init.d/sendmail
-S85gpm -> ../init.d/gpm
-S87iiim -> ../init.d/iiim
-S90canna -> ../init.d/canna
-S90crond -> ../init.d/crond
-S90xfs -> ../init.d/xfs
-S95atd -> ../init.d/atd
-S96readahead -> ../init.d/readahead
-S97messagebus -> ../init.d/messagebus
-S97rhnsd -> ../init.d/rhnsd
-S99local -> ../rc.local
-</screen>
+
<para>
As illustrated in this listing, none of the scripts that actually start and stop the services are located in the <filename>/etc/rc.d/rc5.d/</filename> directory. Rather, all of the files in <filename>/etc/rc.d/rc5.d/</filename> are <firstterm>symbolic links</firstterm> pointing to scripts located in the <filename>/etc/rc.d/init.d/</filename> directory. Symbolic links are used in each of the <filename>rc</filename> directories so that the runlevels can be reconfigured by creating, modifying, and deleting the symbolic links without affecting the actual scripts they reference.
</para>
More information about the docs-commits
mailing list