Systemd
The dominant Linux init system, replacing sequential startup scripts with declarative, parallel, dependency-aware units.
Systemd is the init system used by most mainstream Linux distributions — Debian, Fedora, Arch, Ubuntu — since roughly the early 2010s. It replaced sysvinit's numbered shell scripts with declarative unit files that describe what a service needs rather than the exact sequence to start it, letting the system start independent services in parallel and cutting boot times substantially.
A unit is a small text file — .service for a program, .mount for a filesystem, .timer for a scheduled trigger, .socket for something that starts on first connection — with an explicit After=/Requires= graph instead of a filename number. systemctl status nginx reads that graph and its live state; journalctl -u nginx reads its structured, binary-logged output rather than a scattered pile of text files under /var/log.
Systemd's scope is the recurring objection: it also absorbed device management (udev), network configuration, DNS resolution, login sessions, and time sync, well past what "init" traditionally meant. Proponents call this consistency — one dependency graph, one logging format, one tool — critics call it a monolith that violates the Unix preference for small composable tools. Both are describing the same design honestly.
Its most consequential feature for daily debugging is the systemd unit's automatic restart and resource limits: a service can be told to restart on failure, sandboxed with a private /tmp, or capped on memory, all as unit-file settings rather than code the service itself has to implement.
See also4
Daemon
A long-running background process managed by the operating system's service supervisor.
Systems & Tooling19 connections
Control Groups
The Linux kernel feature that caps and accounts for a process group's CPU, memory, and I/O — the resource-limiting half of a container.
Systems & Tooling16 connections
Cron
Time-based scheduling of recurring jobs, and the reasons scheduled jobs quietly stop working.
Systems & Tooling19 connections
Out-of-Memory Killer
The kernel's last resort when memory is exhausted, killing a process chosen by heuristic, and the userspace daemons that act earlier with better judgment.
Systems & Tooling12 connections
Related6
Nearby in the graph rather than deliberately chosen. Looser, sometimes surprising.
Linked from12
- Boot ProcessSystems & Tooling
The chain of handoffs from power button to login screen, firmware to bootloader to kernel to init, and where each link can break or be verified.
- Control GroupsSystems & Tooling
The Linux kernel feature that caps and accounts for a process group's CPU, memory, and I/O — the resource-limiting half of a container.
- Core DumpSystems & Tooling
A snapshot of a crashed program's memory saved for later inspection, how to get one, how to read one, and why it can leak secrets.
- Exit StatusSystems & Tooling
The small number every process returns when it ends, zero for success and anything else for failure, and the conventions that let shells, CI systems, and init systems act on it.
- Failure DetectionNetworks & Distribution
How the nodes of a distributed system decide that a peer has died, using heartbeats and timeouts, when a crashed node and a slow one look exactly the same from outside.
- Init SystemSystems & Tooling
The first userspace process a kernel starts, and the ancestor of every other process on the machine.
- LoggingTesting & Verification
Recording timestamped events from a running program so people can reconstruct what happened, and how structured logs, levels, and aggregation make them useful at scale.
- Out-of-Memory KillerSystems & Tooling
The kernel's last resort when memory is exhausted, killing a process chosen by heuristic, and the userspace daemons that act earlier with better judgment.
- Rolling ReleaseSystems & Tooling
A distribution model that ships updates continuously instead of in versioned batches, trading stability for currency.
- ShebangSystems & Tooling
The "#!" line at the top of a script that tells the kernel which interpreter should run it, so a text file can be executed like a compiled program, and the portability traps around it.
- Suspend and HibernationSystems & Tooling
The power states that let a computer pause instead of shutting down, keeping memory powered for a fast resume or saving it to disk for a resume with no power at all, and a recurring source of laptop bugs.
- Watchdog TimerSystems & Tooling
A countdown that resets a system unless healthy software keeps restarting it, the last line of defense against hangs in spacecraft, routers, and servers.