In Linux, startup scripts responsible for starting and stopping services are traditionally located in which directory?

In Linux, startup scripts responsible for starting and stopping services are traditionally located in which directory?

• A. /etc/init.d
• B. /boot
• C. /usr/bin
• D. /var/log

Answer: (A)

Traditionally, the startup scripts that handle starting and stopping services in Linux are located in /etc/init.d. These scripts provide start, stop, restart, and status actions for each service, and the init system uses runlevels to decide which ones to run. The actual enabling or disabling of a service at a given runlevel is managed by symbolic links in the rc*.d directories, which point to the scripts in /etc/init.d. Other options like /boot, /usr/bin, and /var/log serve different purposes (boot components, executables, and logs, respectively) and are not where these service control scripts live. Note that newer systems using systemd rely on unit files in /lib/systemd/system and /etc/systemd/system, but the traditional location for SysV-style init is /etc/init.d.

Traditionally, the startup scripts that handle starting and stopping services in Linux are located in /etc/init.d. These scripts provide start, stop, restart, and status actions for each service, and the init system uses runlevels to decide which ones to run. The actual enabling or disabling of a service at a given runlevel is managed by symbolic links in the rc*.d directories, which point to the scripts in /etc/init.d. Other options like /boot, /usr/bin, and /var/log serve different purposes (boot components, executables, and logs, respectively) and are not where these service control scripts live. Note that newer systems using systemd rely on unit files in /lib/systemd/system and /etc/systemd/system, but the traditional location for SysV-style init is /etc/init.d.