Welcome to the Linux Foundation Forum!

2.36 correction

fliker09 Posts: 39
edited October 2017 in LFS211 Class Forum

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


# 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



  • lee42x
    lee42x Posts: 380
    edited October 2017

    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.



  • fliker09
    fliker09 Posts: 39
    edited October 2017

    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.


Upcoming Training