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
- All Categories
- 177 LFX Mentorship
- 177 LFX Mentorship: Linux Kernel
- 754 Linux Foundation IT Professional Programs
- 374 Cloud Engineer IT Professional Program
- 170 Advanced Cloud Engineer IT Professional Program
- 74 DevOps IT Professional Program - Discontinued
- 5 DevOps & GitOps IT Professional Program
- 100 Cloud Native Developer IT Professional Program
- 7.6K Training Courses & Learning Paths
- 2 AI & ML Training
- 1 Blockchain & Decentralized Identity Training
- 5 Cloud & Containers Training
- 1 Cybersecurity Training
- 2 DevOps & Site-Reliability Training
- 1 Linux Kernel Development Training
- 1 Networking Training
- 2 Open Source Best Practice Training
- 2 System Administration Training
- 1 System Engineering Training
- 1 Web & Application Development Training
- 794 Hardware
- 202 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 173 Networking
- 91 Printers & Scanners
- 89 Storage
- 769 Linux Distributions
- 81 Debian
- 68 Fedora
- 22 Linux Mint
- 13 Mageia
- 24 openSUSE
- 150 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 465 Linux System Administration
- 31 Cloud Computing
- 73 Command Line/Scripting
- Github systems admin projects
- 98 Linux Security
- 78 Network Management
- 101 System Management
- 46 Web Management
- 111 Mobile Computing
- 19 Android
- 77 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 393 Off Topic
- 121 Introductions
- 182 Small Talk
- 29 Study Material
- 976 Programming and Development
- 310 Kernel Development
- 648 Software Development
- 990 Software
- 382 Applications
- 182 Command Line
- 5 Compiling/Installing
- 68 Games
- 317 Installation
- Archived
- 2 LFD140 Class Forum
- 1.4K LFS258 Class 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)
