Where are the startup scripts defined in many Unix-like systems?

Where are the startup scripts defined in many Unix-like systems?

• A. /etc/init.d
• B. /start
• C. /usr/local/bin
• D. /etc/rc.local

Answer: (A)

Startup and management of services in many Unix‑like systems is done through a set of scripts located in /etc/init.d. These scripts implement how to start, stop, and manage daemons at boot or during runlevel changes. The init system uses these scripts by calling them with actions like start or stop, and it wires them into the appropriate runlevel directories (such as rc?.d) with symbolic links that determine the order and whether a service should be started or killed during boot and shutdown. This System V init style, with a script per service in /etc/init.d and runlevel links controlling their activation, is the traditional approach. Other options aren’t the central repository for startup scripts: /start isn’t a standard location on Unix-like systems; /usr/local/bin is meant for user‑installed executables, not init scripts. /etc/rc.local exists on some systems to run a final set of commands at the end of the boot process, but it’s optional, not the primary place where startup scripts live, and many systems don’t use it by default. Note that on modern systems some distributions use systemd, which manages services with unit files stored in /etc/systemd/system (and related directories). The /etc/init.d directory is still kept for compatibility with older SysV-style scripts, but the actual startup mechanism in those systems is handled by units rather than traditional init scripts.

Startup and management of services in many Unix‑like systems is done through a set of scripts located in /etc/init.d. These scripts implement how to start, stop, and manage daemons at boot or during runlevel changes. The init system uses these scripts by calling them with actions like start or stop, and it wires them into the appropriate runlevel directories (such as rc?.d) with symbolic links that determine the order and whether a service should be started or killed during boot and shutdown. This System V init style, with a script per service in /etc/init.d and runlevel links controlling their activation, is the traditional approach.

Other options aren’t the central repository for startup scripts: /start isn’t a standard location on Unix-like systems; /usr/local/bin is meant for user‑installed executables, not init scripts. /etc/rc.local exists on some systems to run a final set of commands at the end of the boot process, but it’s optional, not the primary place where startup scripts live, and many systems don’t use it by default.

Note that on modern systems some distributions use systemd, which manages services with unit files stored in /etc/systemd/system (and related directories). The /etc/init.d directory is still kept for compatibility with older SysV-style scripts, but the actual startup mechanism in those systems is handled by units rather than traditional init scripts.