2.36 correction
Isn't it more correct instead of:
# ln -s /etc/init.d/httpd /etc/rc3.d/S85httpd
# rm /etc/rc3.d/S85httpd
# ln -s /etc/init.d/httpd /etc/rc3.d/K25httpd
do:
# ln -s /etc/init.d/httpd /etc/rc3.d/S85httpd
# ln -s /etc/init.d/httpd /etc/rc0.d/K25httpd
# rm /etc/rc3.d/S85httpd /etc/rc0.d/K25httpd
?
Comments
-
Thank you for your input.
This is an example of minimum configuration done manually. Normally the tools "update-rc.d" or "chkconfig" are recomended. The "best" answer is every rc#.d directory should have either a "S" or a "K" link for every service. This allows the service to be selectivly started or stopped when entering any runlevel.
In our example:
# ln -s /etc/init.d/httpd /etc/rc3.d/S85httpd #causes the httpd service to start when entering runlevel 3
# rm /etc/rc3.d/S85httpd # the service will not auto start when entering runlevel 3 but, if we transisition from run level 5 to run level 3 there will be no change on the status of the httpd service. If we explicitly do not want to have the httpd service runing when we transition to run level 3 we need the "K" in the rc3.d directory.
# ln -s /etc/init.d/httpd /etc/rc3.d/K25httpd
The rc0.d directory is used only during OS shutdown processing.
In the current versions of all the major distro's , the SysV startup has been replaced with "systemd" which does not use runlevels.
Regards.
0 -
I understand that there are better ways than doing manual linking and that systemd replaced them all, but I just found your example confusing compared to the ones with upstart and systemd.
0
Categories
- 8.9K All Categories
- 13 LFX Mentorship
- 66 LFX Mentorship: Linux Kernel
- 363 Linux Foundation Boot Camps
- 230 Cloud Engineer Boot Camp
- 70 Advanced Cloud Engineer Boot Camp
- 25 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 844 Training Courses
- 15 LFC110 Class Forum
- 16 LFD102 Class Forum
- 101 LFD103 Class Forum
- 3 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 19 LFD254 Class Forum
- 431 LFD259 Class Forum
- 85 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 16 LFS200 Class Forum
- 692 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 26 LFS241 Class Forum
- 27 LFS242 Class Forum
- 19 LFS243 Class Forum
- 6 LFS244 Class Forum
- 9 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 107 LFS253 Class Forum
- 789 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 51 LFS260 Class Forum
- 78 LFS261 Class Forum
- 13 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 9 LFS268 Class Forum
- 6 LFS269 Class Forum
- 180 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 187 LFW211 Class Forum
- 103 LFW212 Class Forum
- 878 Hardware
- 207 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 723 Linux Distributions
- 81 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 126 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 347 Ubuntu
- 447 Linux System Administration
- 33 Cloud Computing
- 64 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 73 Network Management
- 105 System Management
- 45 Web Management
- 50 Mobile Computing
- 18 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 499 Off Topic
- 119 Introductions
- 193 Small Talk
- 19 Study Material
- 747 Programming and Development
- 240 Kernel Development
- 473 Software Development
- 902 Software
- 247 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 314 Installation
- 20 All In Program
- 20 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)