Name

system-control, systemctl — process system control jobs, sending commands to the system manager and service manager

Synopsis

system-control {command} [arguments or options]

systemctl {command} [arguments or options]

Description

system-control takes a subcommand as command that instructs it on what to do.

For limited systemd compatibility, it is also available as systemctl. Not all subcommands are supported, nor is placing subcommand options before the command.

Note

The compatibility shims for upstart, SunOS, and others are provided by telinit(8). system-control provides no upstart or SunOS compatibility itself, and its various subcommands differ in meaning from most of the subcommands for upstart initctl(8) and SunOS svcadm(8).

It operates in one of two modes, controlled by the {--user} command line option:

  • In "system" mode it operates on system-wide state and services. It potentially communicates with a System Manager process, which must be process #1 and which it expects to recognize the same signals as system-manager(1) does. It potentially communicates with a Service Manager process, such as service-manager(1) via a local domain socket at /run/service-manager/control and via the control/status API of the individual services.

  • In "user" mode it operates on per-user state and services. It potentially communicates with a Session Manager process, which again it expects to recognize the same signals as per-user-manager(1) does. It potentially communicates with a Service Manager process, such as service-manager(1) via a local domain socket at /run/user/$USER/service-manager/control and via the control/status API of the individual services.

Concepts

Services and targets

Services and targets are defined by bundle directories. Although there is no constraint enforced, and system-control simply follows symbolic links, by convention service bundle directories generally live under /etc/service-bundles/services, /run/service-bundles/services, or /var/service-bundles/services; and target bundle directories generally live under /run/service-bundles/targets or /etc/service-bundles/targets.

A service is generally a dæmon process that runs. A target is generally a collection of services that are started/stopped together.

Jobs and actions

The start and stop subcommands construct jobs, which comprise a set of actions. Each action is a start or a stop command to the control API of a service/target. Jobs are composed by starting with an action on a named service, and then following information in the service bundles to related services and targets. The service bundles also determine the order in which the actions are taken.

A start action simply requests that the service manager bring the service/target to the "running" state, if it isn't already there. A stop action, however, is more complex. Initially it requests that the service manager bring the service/target to the "stopped" state (if it isn't already there). However, if that does not happen within 60 seconds, it requests that the service manager send the SIGKILL signal to the service/target.

Bundle directories

A bundle directory contains the command information, dependency information, relationship information, and control/status API for a service. It contains various subdirectories (which can be symbolic links to directories elsewhere):

  • The service/ and supervise/ subdirectories are (respectively) the service and supervise directories for the service, comprising the command information and the control/status API. See service-manager(1) for what service and supervise directories contain. (service-dt-scanner(1) implements a slight extension here, for compatibility.)

    When bundles are on a read-only filesystem, such as a CD-ROM, supervise must be a symbolic link pointing to a directory on a read-write filesystem, since supervise directories must be writable. One might choose a subdirectory of /run/service-bundles/early-supervise/ for example. system-control attempts to create the target of such a symbolic link before attempting to load the service, to avoid a chicken-and-egg situation with "sysinit" services that are set up this way.

  • The wants/, requires/, conflicts/, wanted-by/, stopped-by/, and required-by/ subdirectories comprise dependency or dependency installation information. Each contains a set of symbolic links to other bundle directories for other services.

    • wants/ contains links to services that the current service "wants". Starting the current service implies starting the linked-to service as well.

    • requires/ contains links to services that should be "required-by" the current service when it is enabled. Enabling the service places it in the targets' "required-by" lists, and disabling the service removes it.

    • conflicts/ contains links to services that "conflict" with the current service. Starting the current service implies stopping the linked-to services.

    • required-by/ contains links to services that "require" the current service. Stopping the current service implies stopping the linked-to services as well.

    • wanted-by/ contains links to (standard) targets that should "want" the current service when it is enabled. Enabling the service places it in the targets' wants/ lists, and disabling the service removes it.

    • stopped-by/ contains links to (standard) targets that should "conflict" with the current service when it is enabled. Enabling the service places it in the targets' "conflicts" lists, and disabling the service removes it.

  • The after/ and before/ subdirectories comprise relationship information. Relationships govern the ordering between the individual actions in a start/stop job.

    • after/ contains links to services that should be started after/stopped before the current service when executing a start/stop job.

    • before/ contains links to services that should be started before/stopped after the current service when executing a start/stop job.

Relationships are not the same as dependencies. A service can "want" another service without having any ordering against it with respect to start/stop actions. Indeed, this is a common case for system targets. The normal target, for example, wants/ the server, workstation, multi-user, static-networking , and users targets (and by extension everything that they in their turn wants/), but all of the wanted services are started in parallel with the normal target itself.

Similarly, a service can be ordered with respect to another service without having a dependency from it. For example, both "log" and "main" services are "wanted" by the server and workstation targets, explicitly. The individual "main" services, therefore, only need to be ordered after their corresponding "log" services, and do not wants/ them. ("log" services are first-class citizens in this respect.)

There are no implicit relationships or dependencies in a bundle. The relationships and dependencies are exactly what is explicitly in the filesystem. system-control will fail if the recorded relationships and dependencies are self-contradictory or impossible (such as a service that conflicts with itself, for example).

Bundle search paths and conventional locations

Several subcommands take a list of bundle names . Each name can be the full absolute pathname of a bundle directory or a relative pathname with a directory prefix, in which case it is used as-is, or a bundle directory name without any directory prefix, in which case a set of standard locations is searched for a bundle directory by that name. The search algorithm is as follows:

  • A name that ends in .target is searched for (sans the .target suffix) in the standard locations for target bundles:

    • System-wide target directories:

      1. /run/service-bundles/targets/

      2. /usr/local/etc/service-bundles/targets/

      3. /etc/service-bundles/targets/

      4. /usr/local/share/service-bundles/targets/

      5. /usr/share/service-bundles/targets/

      6. /var/service-bundles/targets/

    • Per-user target directories:

      1. $XDG_RUNTIME_DIR/service-bundles/targets/

      2. $HOME/.config/service-bundles/targets/

  • A name that ends in .service or .socket is searched for (sans those suffixes) in the standard locations for service bundles:

    • System-wide service directories:

      1. /run/service-bundles/services/

      2. /usr/local/etc/service-bundles/services/

      3. /etc/service-bundles/services/

      4. /usr/local/share/service-bundles/services/

      5. /var/local/service-bundles/services/

      6. /var/local/sv/

      7. /usr/share/service-bundles/services/

      8. /var/service-bundles/services/

      9. /var/sv/

      10. /var/svc.d/

      11. /service/

    • Per-user service directories:

      1. $XDG_RUNTIME_DIR/service-bundles/services/

      2. $HOME/.config/service-bundles/services/

  • Any other name is searched for (as-is) in the standard locations for service and for target bundles.

If the path search fails, the name is simply assumed to name a bundle directory in the current directory.

Subcommands

System information subcommands

Synopsis

system-control {version}

For compatibility with uses of initctl, the version subcommand displays the (compiled-in) version of the toolset. It does not contain the string "upstart".

System control subcommands

Synopsis

system-control {reboot} [ -f | --force ]

system-control {halt} [ -f | --force ]

system-control {powercycle} [ -f | --force ]

system-control {poweroff} [ -f | --force ]

system-control {emergency}

system-control {rescue}

system-control {normal}

system-control {init} [--user] [ -o | --update ] [ -s | --single ] [ -b | --emergency ] [-a] [-f] [-z string] [runlevel(s)]

Those subcommands communicate with the system manager to change system state. system-control sends a signal to process #1 using the kill(2) system call. It will fail if it does not have the necessary privileges for sending a signal to that process.

The signals for each subcommand:
commandsignal on FreeBSDsignal on OpenBSDsignal on Linux
haltSIGUSR1unsupportedSIGRTMIN + 3
halt -f SIGRTMIN + 13unsupportedSIGRTMIN + 13
poweroffSIGUSR2unsupportedSIGRTMIN + 4
poweroff -f SIGRTMIN + 14unsupportedSIGRTMIN + 14
rebootSIGINTSIGINTSIGRTMIN + 5
reboot -f SIGRTMIN + 15SIGTSTPSIGRTMIN + 15
powercycleSIGWINCHunsupportedSIGRTMIN + 7
powercycle -f SIGRTMIN + 17unsupportedSIGRTMIN + 17
emergencySIGRTMIN + 2unsupportedSIGRTMIN + 2
rescueSIGRTMIN + 10 then SIGRTMIN + 1unsupportedSIGRTMIN + 10 then SIGRTMIN + 1
normalSIGRTMIN + 10 then SIGRTMIN + 0unsupportedSIGRTMIN + 10 then SIGRTMIN + 0
init [ 2 | 3 | 4 | 5 | m | auto ]SIGRTMIN + 10 then SIGRTMIN + 0unsupportedSIGRTMIN + 10 then SIGRTMIN + 0
init 1 | S | s | single SIGRTMIN + 10 then SIGRTMIN + 1unsupportedSIGRTMIN + 10 then SIGRTMIN + 1
init -s SIGRTMIN + 2unsupportedSIGRTMIN + 10 then SIGRTMIN + 1
init -b unsupportedunsupportedSIGRTMIN + 2
init b | emergency SIGRTMIN + 2unsupportedSIGRTMIN + 2
init H | h SIGUSR1SIGUSR1SIGRTMIN + 3
init C | c SIGWINCHunsupportedSIGRTMIN + 7
init 0 SIGUSR2SIGUSR2SIGRTMIN + 4
init 6 SIGINTSIGINTSIGRTMIN + 5

Note

OpenBSD lacks the ability to send real-time signals.

Exactly how the system power cycles, powers off, halts, reboots, switches to normal, emergency, or rescue modes, and so forth is entirely up to whatever is running as process #1, which is expected to be in charge of system state. These subcommands do nothing except send the signals to command the system manager. They do not directly enact any system state change themselves. In part this is because that would open up the possibility of the service manager killing the process that was (partway through) enacting the state changes, if a state change happened to affect the service running the system-control command.

The [--force] command line argument is used within the various targets and is intended to cause the system manager to proceed directly to the finalization action.

The init subcommand is spawned by system-manager(8) and per-user-manager(8) as their initial action. They pass it the command line arguments that they themselves were invoked with. As such, its command line syntax is modelled on what boot loaders and kernels tend to supply to process #1, which is a largely undocumented and non-standardized mixture of old-style runlevels and options.

In normal and rescue modes it sends two signals to process #1, instituting a two-phase initialization sequence similar to the FILESYSTEMS milestone mechanism in BSD operating systems. The first phase, the sysinit target, is expected to initialize as much of the system as necessary so that the second phase, the normal or rescue target, can find all service and target bundles, including those that are not on the root filesystem.

Caution

There is no q runlevel. This is deliberate. Its use case is running telinit q after updating /etc/ttys or /etc/inittab. Any script that is updating those files and then expecting the system manager to re-read them is not targetting the correct configuration mechanisms, and is in error.

LILO, the FreeBSD loader(8), GRUB, and others may cause -a or -f options to be passed. Their meanings are non-standard, largely or even wholly undocumented, inconsistent across platforms and toolsets, considered obsolete in their original forms, and without application here. The -z option is a dummy space-taker that is also used by such systems. All three options are ignored. The --update command line option is reserved for future use.

job subcommands

Synopsis

system-control { start | activate } [--colour] [--verbose] [--pretend] [names]

system-control { stop | deactivate } [--colour] [--verbose] [--pretend] [names]

system-control {isolate} [--colour] [--verbose] [--pretend] [names]

system-control {reset} [--colour] [--verbose] [--pretend] [names]

These subcommands process one or more jobs, sending messages to the service manager to start or to stop one or more services. Jobs may also involve invoking any number of configurable actions. Jobs processing tries to ensure that service dependencies are correctly maintained and processed. To control services directly and individually without regard for dependencies, use service-control(8).

The --verbose command line option causes information about actions taken and blocked/unblocked services to be written to standard error as jobs are processed. If the standard error is a terminal, system-control uses whatever it can find via the TerminalCapabilities(3) library to display various parts of the output in different colours, highlighting different events in different colours. The --colour command line option tells it to do this unconditionally, even if its standard error is not a terminal. The --pretend command line option tells it to only pretend that it is taking actions, and not actually take them.

The reset command is intended to be used by package installer programs. It is translated into either start or stop according to whether the service is enabled or disabled; and can be thought of, if one likes, as "reset to however the service is configured to be at bootstrap". This allows package installers to remain in blissful ignorance of whether a service should be started or stopped after installing the package for it. Instead, the package installer simply executes the preset command and then the reset command and the service is started or stopped according to whatever the administrator has chosen.

Caution

The isolate subcommand exists for compatibility, and is equivalent to start. Avoid using it.

service autoboot configuration subcommands

Synopsis

system-control {enable} [names]

system-control {disable} [names]

system-control {preset} [--prefix prefix] [--no-system] [--no-rcconf] [--rcconf-file filename] [--ttys] [--dry-run] [names]

These subcommands enable or disable one or more services or targets, so that they do or do not automatically start when one of the standard targets is started and automatically stop when the shutdown standard target is started.

Each service bundle specifies a (symbolically linked) list of target bundles in its wanted-by/ directory. Usually these will be the workstation, server, users, or multi-user standard targets. For each bundle, enabling the service involves symbolically linking its bundle directory into the target bundle's wants/ list, and disabling the service involves removing that link.

Each service bundle also specifies a (symbolically linked) list of target bundles in its stopped-by/ directory. Usually these will be the shutdown standard target. For each bundle, enabling the service involves symbolically linking its bundle directory into the target bundle's conflicts/ and after/ lists, and disabling the service involves removing those links.

The preset command is intended to be used by package installer programs. It is translated into either enable or disable according to a system/administrator-supplied preset flag (unless the --dry-run command line argument is used, causing it to take no actual action). This allows package installers to remain in blissful ignorance of whether a service should be enabled or disabled after installing the package for it. Instead, the package installer simply executes the preset command and the service is set to whatever enabled or disabled status the administrator has chosen.

The service/socket/target that is preset is prefixname, with prefix specifiable via the --prefix command line argument. Preset information can be taken from one of several sources:

  • (unless the --no-system command line option is set) systemd and system-manager preset information given in *.preset files. There are different sets of files for per-user and system-wide service management.

    • System-wide preset files are located in the following directories:

      1. /usr/local/etc/system-control/presets/

      2. /etc/system-control/presets/

      3. /etc/systemd/system-preset/

      4. /usr/local/share/system-control/presets/

      5. /usr/local/lib/systemd/system-preset/

      6. /usr/share/system-control/presets/

      7. /usr/lib/systemd/system-preset/

      8. /lib/systemd/system-preset/

    • Per-user preset files are located in the following directories:

      1. /usr/local/etc/system-control/user-presets/

      2. /etc/system-control/user-presets/

      3. /etc/systemd/user-preset/

      4. $HOME/.config/system-control/presets/

      5. /usr/local/share/system-control/user-presets/

      6. /usr/local/lib/systemd/user-preset/

      7. /usr/share/system-control/user-presets/

      8. /usr/lib/systemd/user-preset/

      9. /lib/systemd/user-preset/

    Contrary to its doco, systemd has four places for system-wide/user-level preset files, which form part of these lists. In addition to those locations, preset looks in extra directories where systemd presets can be overridden by system-control-specific information; allowing a system administrator or package writer to preset things one way for systemd and another way for the preset command. These extra directories follow the more conventional scheme of /etc, /usr/share, and /usr/local/etc for administrator-set, operating-system-set, and application-software-set stuff.

    As with systemd, earlier preset directories override later ones; the contents of files with lexically earlier names override the contents of files with lexically later names; and the default state, in the absence of an explicit preset, is "enabled". Directives are matched against prefixname.

  • (unless the --no-rcconf command line option is set) rc.conf(5) preset information, specifically the name_enable variable, interpreting the values true, 1, yes, and on as enable, and any other values (including specifically false, 0, no, and off) as disable.

    By default in system-wide mode the /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local files are used, but the --rcconf-file command line option overrides that list with the single replacement file filename. The default for per-user mode is the $HOME/.config/rc.conf file.

    The variable names are matched against just name to allow one to use a main service name as name and combine it with a log service template prefix such as cyclog@ or s6-multilog@, on the grounds that traditional /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local contents do not make explicit provision for separate logging services.

  • (if the --ttys command line option is set) /etc/ttys preset information, specifically the on and off flags as enable and disable, respectively. The onifconsole flag is also recognized and processed with reference to the currently active console device (on BSD systems only). If /etc/ttys does not exist, as is usually the case on Linux operating systems, all TTYs default to preset disabled.

    The terminal names are matched against just name. This allows one to use an ordinary TTY device name as name and combine it with a "templatized" bundle name prefix such as ttylogin@, getty@, or agetty@.

  • (if the --fstab command line option is set) /etc/fstab preset information, specifically the noauto flag as disable.

    The device and directory names are matched against just name, after unescaping it. This allows one to use an ordinary device or directory name as name and combine it with a "templatized" bundle name prefix such as mount@, fsck@, swap@, or dump@. This is designed in particular for use with service bundles generated by the convert-fstab-services subcommand.

service status/control subcommands

Synopsis

system-control {status} [names]

system-control {show} [names]

system-control {find} [names]

system-control { try-restart | try-reload-or-restart | condrestart | force-reload } [names]

system-control {hangup} [names]

system-control {is-active} [names]

system-control {is-loaded} [names]

system-control {is-enabled} [names]

system-control {unload-when-stopped} [names]

system-control takes each of the names , searches for the corresponding service bundle directory, constructs a list of directory names, and chains to other commands with those directory names as directories arguments:

status/control commands:
subcommandchains to
status service-status(1) -- directories
show service-show(1) -- directories
show-json service-show(1) --json -- directories
find ls(1) -1d -- directories
[ try-restart | try-reload-or-restart | force-reload | condrestart ] service-control(1) --terminate -- directories
hangup service-control(1) --hangup-main -- directories
unload-when-stopped service-control(1) --exit -- directories
is-active service-is-up(1) -- directories
is-loaded service-is-ok(1) -- directories
is-enabled service-is-enabled(1) -- directories

script conversion subcommand

For brevity, this is documented on a standalone convert-systemd-units(1) manual page.

fstab conversion subcommand

For brevity, this is documented on a standalone convert-fstab-services(1) and write-volume-service-bundles(1) manual page.

conversion utility subcommand

Synopsis

system-control {escape} [--alt-escape] [--prefix prefix] {name}

The escape subcommand takes each name and converts it using the escaping rules used in the convert-systemd-units subcommand. Each escaped name is written to standard output, separated from its predecessor (if any) by a space and prefixed with prefix (which is not escaped).

The --alt-escape option causes the same selection of an alternative escaping algorithm as with the command line option of the same name for the convert-systemd-units subcommand.

Nagios plug-in subcommand

Synopsis

system-control {nagios-check-service} [--min-seconds seconds] [--critical-if-below-min] {name}

This subcommand is intended for use as a Nagios plug-in. It queries the status API in the bundle directory for service/target name .

  • If the service is up for longer than seconds seconds it returns a Nagios "OK" status.

  • If the service is up, but for less than seconds seconds it returns a Nagios "WARNING" status and prints a line containing the service bundle directory name. It does the same if the service is still in the process of being loaded by the service manager, or in the starting or stopping states. The --critical-if-below-min command line option changes the status returned for such up services to "CRITICAL", but does not alter the treatment of starting or stopping services.

  • If the service is unexpectedly down or unloaded, if the status API reports the service running in the future (because of clock skew somewhere), or if the service is in the failing state, it returns a Nagios "CRITICAL" status and prints a line containing the service bundle directory name.

Kernel module management subcommands

Synopsis

system-control {load-kernel-module} {module}

system-control {unload-kernel-module} {module}

These subcommands provide a minimal operating-system-neutral kernel module loading and unloading mechanism, for use in cross-platform service bundles. They devolve to the appropriate operating system commands, which are kldload(8) and kldunload(8) on BSD and modprobe(8) (without or with the --remove option) on Linux.

service program dump subcommands

Synopsis

system-control {print-service-scripts} [names]

system-control {cat} [names]

system-control takes each of the names , searches for the corresponding service bundle directory, changes to the corresponding service directory, and runs grep(1) to dump the contents of the start, stop, run, and restart files.

service environment manipulation subcommands

Synopsis

system-control {set-service-env} [--full] {name} {var} [value]

system-control {print-service-env} [--full] {name} [var]

If the name service has an environment template subdirectory named env/ (in the format understood by envdir(1)), these subcommands can be used to manipulate that template.

  • set-service-env name var value sets var to value in the template, the change not (of course) affecting any currently running service.

  • set-service-env name var specifies that the template unset var, the change not (of course) affecting any currently running service.

  • print-service-env name var prints (only) the value of var from the template.

  • print-service-env name prints the whole template as list of var=value entries.

The --full command-line option switches to an alternative format for the environment template subdirectory, as understood by envdir(1) when its option of the same name is used.

filesystem table query subcommands

Synopsis

system-control {get-mount-what} [where]

system-control {get-mount-where} [what]

These subcommands query the flat file table in /etc/fstab (see fstab(5)). They fill a gap left by the getent(1) command, which has no subcommand for reading this table. Like that command, they query the on-disc administrative database of what is configured to be mounted; not the kernel's list of currently active mounts.

  • For a given mount-point where get-mount-what prints the volume that is configured to be mounted upon it.

  • For a given volume what get-mount-where prints the point where it is configured to be mounted.

Standard targets

Several standard targets are defined. They conventionally live in the /etc/service-bundles/targets/ directory.

startup

These standard targets are (indirectly) started by the init subcommand.

normal

This target is the normal target started by the init subcommand. This should bring up with it all of the services involved in the normal operation of the system, and an administrator-defined set of multiple login user interfaces that may include both TUI and GUI login prompts.

It wants/ the workstation, server, and multi-user targets. Thus starting it starts the union of all services wanted by those targets. It is not ordered with respect to those targets. So in the absence of orderings in between the individual services wanted by those targets, defined in their bundles, all wanted workstation, server, and multi-user services are brought up in parallel.

emergency

This target is the target started by the init subcommand with the -b option. Starting it is intended to bring up the system in "emergency mode", bringing up no services, mounting no (non-system) volumes, and bringing up just "emergency mode" services, such as a secure login on the default terminal.

It wants/ no other targets or services. So in "emergency mode" (if nothing else has been started) only the system filesystems are available, and not necessarily even read-write.

rescue

This target is the target started by the init subcommand with the -s option. Starting it is intended to bring up the system in "rescue mode", bringing up with it the fundamental system initialization services and a secure login user interface.

It wants/ the sysinit target, but not the basic target.

update

This target is the target started by the init subcommand with the --update option. Starting it is intended to bring up the system in "update mode", bringing up with it the fundamental system initialization services and the system update utility.

It wants/ the sysinit target, but not the basic target.

shutdown

The poweroff, powercycle, halt, and reboot subcommands invoke several standard targets indirectly.

poweroff, powercycle, halt, reboot

These four targets both wants/ the shutdown target and order themselves to start after it. Thus starting them shuts down all services and then, once this has been done, starts these targets. They are usually started by the System Manager, in response to system control commands requesting system reboot, halt, or power off. When they (finally) start, they invoke the reboot, halt, powercycle, and poweroff subcommands of system-control with the {-f} command-line option. This signals the System Manager to enact the actual reboot, halt, power-cycle, or power-off action.

For example: When system-manager(8) is process #1, system halt operates as follows:

  1. The superuser runs system-control {halt}. This sends SIGUSR1 (on BSD) or SIGRTMIN + 3 (on Linux) to the system manager process.

  2. In response to that signal, the system manager runs system-control {activate} halt .

  3. system-control does everything necessary for activating the halt target, including stopping all other (conflicting) services and targets. In the service control ordering starting the halt target comes after processing every other service, because of the ordering between halt and shutdown and between shutdown and everything else.

  4. When the halt target is finally started it runs system-control {halt} {-f}. This sends SIGRTMIN + 13 to the system manager process.

  5. In response to that signal, the system manager performs the finalization action of actually telling the operating system kernel to halt the system, after various standard system shutdown actions such as flushing the filesystem cache.

Other standard targets are started by telinit(1).

service collections

User-supplied services and targets that are auto-started at system bootstrap should list themselves in the wants/ and conflicts/ lists of subordinate targets (via the enable and disable subcommands). These targets are usually not started explicitly.

workstation

All services that normally form part of bringing the system up as a "workstation" should be listed in this target's wants/ list. Such services will include things such as the cron(1) dæmon. This target wants/ the basic target, so starting it (directly or indirectly) will bring the basic system up. It is a collection that is used to group services, but is not an ordering milestone and has no before/ or after/ relationships.

server

All services that normally form part of bringing the system up as a "server" should be listed in this target's wants/ list. Such services will include things such as HTTP/FTP/SMTP dæmons, and dæmons that provide services over the network. This target wants/ the basic target, so starting it (directly or indirectly) will bring the basic system up. It is a collection that is used to group services, but is not an ordering milestone and has no before/ or after/ relationships.

multi-user

All services that normally form part of bringing up multi-user logins should be listed in this target's wants/ list. Such services will include things such as the login services for terminals (real and virtual) and X. This target wants/ the basic target, so starting it (directly or indirectly) will bring the basic system up. It is a collection that is used to group services, but is not an ordering milestone and has no before/ or after/ relationships.

shutdown

Starting this target is intended to shut down all running normal services. All normal services should be in this target's conflicts/ list. It is also an ordering milestone, in that all services listed in its conflicts/ list should also be listed in its after/ list. shutdown is then listed in the after/ list of the poweroff, powercycle, halt, and reboot target to ensure that they are only started after the system has entered "shutdown mode".

unmount

Starting this target is intended to unmount all filesystems, both local and remote. All mount@* services should be in this target's conflicts/ list. unmount is then listed in the after/ list of the poweroff, powercycle, halt, and reboot target to ensure that they are only started after the system has unmounted all filesystems.

core subordinate targets

Core services and targets are incorporated into a set of further subordinate targets.

Pure collections

These core targets are solely collections. They are a mechanism for listing a wants/ dependency on a group of services without explicitly enumerating every single member of the group. They are not ordering milestones and have no before/ or after/ relationships.

basic

This target implies the "basic" system, excluding all workstation, server, and multi-user services. It wants/ the sysinit target.

static-networking

This target implies the static setup/teardown of network interfaces and routing. It wants/ all of the generated static_protocol@id services.

sysinit

All fundamental system initialization services and steps should be listed in this target's wants/ list. Such services will include things such as the hostname service that runs set-dynamic-hostname(1), the machine-id service that runs setup-machine-id(1), the local-fs target, and the remote-fs target.

swapauto

This target is wanted by "sysinit". All "auto" "swap" services should be listed in its wants/ lists.

swaplate

This target is wanted by "sysinit". All "late" "swap" services should be listed in its wants/ lists.

dumpauto

This target is wanted by "sysinit". All "dump" services should be listed in its wants/ lists.

finish-install, finish-update

These targets wants/ the various services that finish a system install or a system upgrade.

Pure ordering milestones

These core targets are not collections; their wants/ lists should be empty. They are solely ordering milestones, listed in the before/ and after/ lists of other services. They exist because services that need to occur before them do not have another way to hold back the services that need to occur after they become ready.

Conventionally, they are brought in only if the services that want to order before/ them are themselves brought in, and it is those services that list these milestones in their wants/ lists. This is only a convention, however. There is no technical reason that it could not be all of the services that want to order after/ the milestones that list them in their wants/ lists. It is simply the case that something must bring the target in, for the orderings to actually take effect.

local-fs-pre

This "local filesystems precursor" target exists because system initialization services that need to occur before any filesystem checks or mounts, usually special services that initialize an interactive UI for fsck(1), do not have another way to hold the checks/mounts from commencing until they are done. Such services should list this target in their wants/ and before/ lists. Local filesystem checks, decryptions, and mounts should list this target in their after/ lists, so that they order relative to it if the target is brought in but do not themselves bring it in.

fs-servers

This "filesystems servers" target exists in order to ensure that remote filesystem mounts of volumes on the local machine work, by ordering them after the startup of any filesystem servers (e.g. SAMBA or NFS server dæmons). Such server services should list this target in their wants/ and before/ lists. Remote filesystem mounts should list this target in their after/ lists, so that they order relative to it if the target is brought in but do not themselves bring it in.

multi-user-pre

This "multi-user precursor" target exists for services that need to start/execute before any multi-user login. Such services should list this target in their wants/ and before/ lists. Login services should list this target in their after/ lists.

name-services

This target exists because some name/address services lookup clients cannot be caused via the client-server communications mechanism itself to block indefinitely until the server is ready; and so have to have an explicit ordering to order them after any respective servers. One lists name-services in the wants/ and after/ list of a service or target to ensure that it is only brought up after such name/address lookup services are available. All services that are involved in providing local name/address lookup services should be listed in its after/.

databases

This "database servers" target exists because some database clients cannot be caused via the client-server communications mechanism itself to block indefinitely until the server is ready; and so have to have an explicit ordering to order them after any respective servers. One lists databases in the wants/ and after/ lists of a service or target to ensure that it is only brought up after such database services are available. All services that are involved in providing database services should list it in their before/ lists.

machine-id

One lists machine-id in the wants/ and after/ lists of a service or target to ensure that it is only brought up after the machine ID is available. All services that are involved in setting up the machine ID should list it in their before/ lists.

hostname

One lists hostname in the wants/ and after/ lists of a service or target to ensure that it is only brought up after the dynamic hostname has been initialized. All services that are involved in initializing up the dynamic hostname should list it in their before/ lists.

Both collections and ordering milestones

Generally, with some exceptions, all services listed in these targets' wants/ lists should also be listed in their after/ lists.

local-fs

This "local filesystems" target lists all system initialization services and steps for checking and mounting local filesystems, including remounting the root filesystem in read-write mode. One can thus list local-fs in the after/ list of a service or target to ensure that it is only brought up after local filesystems have been mounted and checked.

Note that services encompassed by this target may not rely upon filesystems being checked and mounted, nor upon the root filesystem being mounted read-write. To handle the latter, in particular, their supervise/ subdirectories should be symbolic links to a suitable subdirectory of /run/service-bundles/early-supervise.

remote-fs

This "remote filesystems" target lists all system initialization services and steps for checking and mounting remote filesystems. One can thus list remote-fs in the after/ list of a service or target to ensure that it is only brought up after remote filesystems have been mounted and checked.

reboot-after-install, reboot-after-update

These target wants/ the reboot target. They are ordering milestones, with all finish-install/finish-update services expected to order themselves before/ these targets.

Author

Jonathan de Boyne Pollard