Changeset fa914e5 for chapter07/usage.xml
- Timestamp:
- 08/29/2001 07:50:53 PM (23 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 2bdc67d
- Parents:
- 2b1174be
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/usage.xml
r2b1174be rfa914e5 36 36 37 37 <para>There are a number of directories under /etc that look like like rc?.d 38 where ? is the number of the runlevel and rcS.d. A user might take a look 39 at one of 40 them (after this chapter is finished, right now there's nothing 41 there yet). There are a number of symbolic links. Some begin with an K, 42 the others begin with an S, and all of them have three numbers following 43 the initial letter. The K means to stop (kill) a service, and the S means 44 to start a service. The numbers determine the order in which the scripts 45 are run, from 000 to 999; the lower the number the sooner it gets 46 executed. When init switches to another runlevel, the appropriate 47 services get killed and others get started.</para> 38 where ? is the number of the runlevel and rcS.d which contain a number of s 39 ymbolic links. Some begin with an K, the others begin with an S, and all 40 of them have three numbers following the initial letter. The K means to 41 stop (kill) a service, and the S means to start a service. The numbers 42 determine the order in which the scripts are run, from 000 to 999; the 43 lower the number the sooner it gets executed. When init switches to 44 another runlevel, the appropriate services get killed and others get 45 started.</para> 48 46 49 47 <para>The real scripts are in /etc/init.d. They do all the work, and the 50 symlinks all point to them. Killing links and starting 51 links point to the same script in /etc/init.d. That's because the scripts52 ca n be called with different parameters like start, stop, restart, reload,48 symlinks all point to them. Killing links and starting links point to 49 the same script in /etc/init.d. That's because the scripts can be 50 called with different parameters like start, stop, restart, reload, 53 51 status. When a K link is encountered, the appropriate script is run with 54 52 the stop argument. When a S link is encountered, the appropriate script 55 53 is run with the start argument.</para> 54 55 <para>There is one exception. Links that start with an S in the 56 rc0.d and rc6.d directories will not cause anything to be started. They 57 will be called with the paramater <emphasis>stop</emphasis> to stop 58 something. The logic behind it is that when you are going to reboot or 59 halt the system, you don't want to start anything, only stop the 60 system.</para> 56 61 57 62 <para>These are descriptions of what the arguments make the
Note:
See TracChangeset
for help on using the changeset viewer.