Differences between System V and systemd: Difference between revisions
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
System V uses a set of init shell scripts to start and stop services. They are stored under <code>/etc/init.d</code> directory, and they are executed by the <code>init</code> process. | System V uses a set of init shell scripts to start and stop services. They are stored under <code>/etc/init.d</code> directory, and they are executed by the <code>init</code> process. | ||
<code>systemd</code> uses [[Systemd_Concepts#Units_and_Unit_Files|unit files]], which are configuration files, not executable scripts. They describe how to start and stop services. They are stored in <code>/lib/systemd/system</code> | <code>systemd</code> uses [[Systemd_Concepts#Units_and_Unit_Files|unit files]], which are configuration files, not executable scripts. They describe how to start and stop services. They are stored in <code>/usr/lib/systemd/system</code> and they are managed by the <code>systemd</code> process. | ||
System V starts services sequentially. <code>systemd</code> starts services in parallel, being aware of the service dependency DAG. | |||
Revision as of 21:08, 19 August 2023
Internal
Overview
Both System V and systemd are init systems, used to manage processes and services on Linux systems. An init system is responsible for starting and stopping services, controlling runlevels, and providing a way to start and stop processes.
System V uses a set of init shell scripts to start and stop services. They are stored under /etc/init.d directory, and they are executed by the init process.
systemd uses unit files, which are configuration files, not executable scripts. They describe how to start and stop services. They are stored in /usr/lib/systemd/system and they are managed by the systemd process.
System V starts services sequentially. systemd starts services in parallel, being aware of the service dependency DAG.