X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.xml;h=bf7a7a6f67209c7dc4384d1e3c9af46ef1b191b4;hp=a184b1a401ede3c202e2e4b5879d49dde43bf270;hb=f280bcfb21aacce03abf17b3ad732c1351df42b9;hpb=cb07866b1b7c11e687a322d70dd9f9d73bbbe488 diff --git a/man/systemd.xml b/man/systemd.xml index a184b1a40..bf7a7a6f6 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -21,7 +21,8 @@ along with systemd; If not, see . --> - + systemd @@ -45,7 +46,7 @@ systemd init - systemd System and Service Manager + systemd system and service manager @@ -78,7 +79,7 @@ the configuration file system.conf, otherwise user.conf. See - systemd.conf5 + systemd-system.conf5 for more information. @@ -88,13 +89,6 @@ The following options are understood: - - - - - Prints a short help - text and exits. - @@ -112,25 +106,11 @@ configuration items understood in unit definition files. - - - - Extract D-Bus - interface introspection data. This is - mostly useful at install time - to generate data suitable for the - D-Bus interfaces - repository. Optionally the interface - name for the introspection data may be - specified. If omitted, the - introspection data for all interfaces - is dumped. - Set default unit to - activate on startup. If not specified + activate on startup. If not specified, defaults to default.target. @@ -138,11 +118,13 @@ - Tell systemd to run a - system instance (resp. user - instance), even if the process ID is - not 1 (resp. is 1), i.e. systemd is - not (resp. is) run as init process. + For , + tell systemd to run a + system instance, even if the process ID is + not 1, i.e. systemd is not run as init process. + does the opposite, + running a user instance even if the process + ID is 1. Normally it should not be necessary to pass these options, as systemd automatically detects the mode it is @@ -198,10 +180,8 @@ target. Argument must be one of , , - , , , - , . @@ -209,7 +189,7 @@ Set log level. As argument this accepts a numerical log - level or the well-known syslog3 + level or the well-known syslog3 symbolic names (lowercase): , , @@ -225,7 +205,7 @@ Highlight important log messages. Argument is a boolean - value. If the argument is omitted it + value. If the argument is omitted, it defaults to . @@ -245,11 +225,11 @@ Sets the default - output resp. error output for all - services and sockets, i.e. controls + output or error output for all + services and sockets, respectively. That is, controls the default for - resp. + and (see systemd.exec5 for details). Takes one of @@ -270,6 +250,9 @@ to . + + + @@ -277,25 +260,27 @@ Concepts systemd provides a dependency system between - various entities called "units". Units encapsulate - various objects that are relevant for system boot-up - and maintenance. The majority of units are configured - in unit configuration files, whose syntax and basic - set of options is described in + various entities called "units" of 12 different + types. Units encapsulate various objects that are + relevant for system boot-up and maintenance. The + majority of units are configured in unit configuration + files, whose syntax and basic set of options is + described in systemd.unit5, however some are created automatically from other - configuration or dynamically from system state. Units - may be 'active' (meaning started, bound, plugged in, - ... depending on the unit type, see below), or - 'inactive' (meaning stopped, unbound, unplugged, ...), - as well as in the process of being activated or - deactivated, i.e. between the two states (these states - are called 'activating', 'deactivating'). A special - 'failed' state is available as well which is very - similar to 'inactive' and is entered when the service - failed in some way (process returned error code on - exit, or crashed, or an operation timed out). If this - state is entered the cause will be logged, for later + configuration, dynamically from system state or + programmatically at runtime. Units may be "active" + (meaning started, bound, plugged in, ..., depending on + the unit type, see below), or "inactive" (meaning + stopped, unbound, unplugged, ...), as well as in the + process of being activated or deactivated, + i.e. between the two states (these states are called + "activating", "deactivating"). A special "failed" + state is available as well, which is very similar to + "inactive" and is entered when the service failed in + some way (process returned error code on exit, or + crashed, or an operation timed out). If this state is + entered, the cause will be logged, for later reference. Note that the various unit types may have a number of additional substates, which are mapped to the five generalized unit states described @@ -304,7 +289,7 @@ The following unit types are available: - Service units, which control + Service units, which start and control daemons and the processes they consist of. For details see systemd.service5. @@ -361,6 +346,18 @@ objects change or are modified. See systemd.path5. + Slice units may be used to + group units which manage system processes + (such as service and scope units) in a + hierarchical tree for resource management + purposes. See + systemd.slice5. + + Scope units are similar to + service units, but manage foreign processes + instead of starting them as well. See + systemd.scope5. + Units are named as their configuration @@ -385,7 +382,7 @@ and ordering dependencies are placed between two units. Also note that the majority of dependencies are implicitly created and maintained by systemd. In most - cases it should be unnecessary to declare additional + cases, it should be unnecessary to declare additional dependencies manually, however it is possible to do this. @@ -407,7 +404,7 @@ multi-user.target (for limited console-only boots for use in embedded or server environments, or similar; a subset of - graphical.target). However it is at the discretion of + graphical.target). However, it is at the discretion of the administrator to configure it as an alias to any other target unit. See systemd.special7 @@ -417,7 +414,7 @@ individual Linux control groups named after the unit which they belong to in the private systemd hierarchy. (see cgroups.txt + url="https://www.kernel.org/doc/Documentation/cgroups/cgroups.txt">cgroups.txt for more information about control groups, or short "cgroups"). systemd uses this to effectively keep track of processes. Control group information is @@ -425,7 +422,7 @@ file system hierarchy (beneath /sys/fs/cgroup/systemd/), or in tools such as - ps1 + ps1 (ps xawf -eo pid,user,cgroup,args is particularly useful to list all processes and the systemd units they belong to.). @@ -465,14 +462,14 @@ Systemd contains native implementations of various tasks that need to be executed as part of the - boot process. For example, it sets the host name or + boot process. For example, it sets the hostname or configures the loopback network device. It also sets up and mounts various API file systems, such as /sys or /proc. For more information about the concepts and - ideas behind systemd please refer to the Original Design Document. @@ -489,12 +486,12 @@ Specification. Systems which invoke systemd in a container - resp. initrd environment should implement the + or initrd environment should implement the Container - Interface resp. or initrd - Interface specifications. + Interface specifications, respectively. @@ -527,7 +524,9 @@ disable commands of the systemctl1 - tool. + tool. Full list of directories is provided in + systemd.unit5. + @@ -556,7 +555,9 @@ tool can handle both global (i.e. for all users) and private (for one user) enabling/disabling of - units. + units. Full list of directories is provided in + systemd.unit5. + @@ -599,7 +600,7 @@ - SIGTERM + SIGTERM Upon receiving this signal the systemd system manager @@ -619,7 +620,7 @@ - SIGINT + SIGINT Upon receiving this signal the systemd system manager will @@ -631,11 +632,11 @@ systemd user managers treat this signal the same way as - SIGTERM. + SIGTERM. - SIGWINCH + SIGWINCH When this signal is received the systemd system manager @@ -651,7 +652,7 @@ - SIGPWR + SIGPWR When this signal is received the systemd manager @@ -663,7 +664,7 @@ - SIGUSR1 + SIGUSR1 When this signal is received the systemd manager will try @@ -672,7 +673,7 @@ - SIGUSR2 + SIGUSR2 When this signal is received the systemd manager will log @@ -683,7 +684,7 @@ - SIGHUP + SIGHUP Reloads the complete daemon configuration. This is mostly @@ -692,7 +693,7 @@ - SIGRTMIN+0 + SIGRTMIN+0 Enters default mode, starts the default.target @@ -702,7 +703,7 @@ - SIGRTMIN+1 + SIGRTMIN+1 Enters rescue mode, starts the @@ -713,7 +714,7 @@ - SIGRTMIN+2 + SIGRTMIN+2 Enters emergency mode, starts the @@ -724,7 +725,7 @@ - SIGRTMIN+3 + SIGRTMIN+3 Halts the machine, starts the @@ -735,7 +736,7 @@ - SIGRTMIN+4 + SIGRTMIN+4 Powers off the machine, starts the @@ -746,7 +747,7 @@ - SIGRTMIN+5 + SIGRTMIN+5 Reboots the machine, starts the @@ -757,7 +758,7 @@ - SIGRTMIN+6 + SIGRTMIN+6 Reboots the machine via kexec, starts the @@ -768,31 +769,31 @@ - SIGRTMIN+13 + SIGRTMIN+13 Immediately halts the machine. - SIGRTMIN+14 + SIGRTMIN+14 Immediately powers off the machine. - SIGRTMIN+15 + SIGRTMIN+15 Immediately reboots the machine. - SIGRTMIN+16 + SIGRTMIN+16 Immediately reboots the machine with kexec. - SIGRTMIN+20 + SIGRTMIN+20 Enables display of status messages on the console, as @@ -803,7 +804,7 @@ - SIGRTMIN+21 + SIGRTMIN+21 Disables display of status messages on the console, as @@ -814,45 +815,48 @@ - SIGRTMIN+22 - SIGRTMIN+23 + SIGRTMIN+22 + SIGRTMIN+23 Sets the log level to debug - (resp. info on - SIGRTMIN+23), as + (or info on + SIGRTMIN+23), as controlled via systemd.log_level=debug - (resp. systemd.log_level=info - on SIGRTMIN+23) on + (or systemd.log_level=info + on SIGRTMIN+23) on the kernel command line. - SIGRTMIN+26 - SIGRTMIN+27 - SIGRTMIN+28 - SIGRTMIN+29 + SIGRTMIN+24 + + Immediately exits the + manager (only available for --user + instances). + + + + SIGRTMIN+26 + SIGRTMIN+27 + SIGRTMIN+28 Sets the log level to - journal-or-kmsg - (resp. console on - SIGRTMIN+27; - resp. kmsg on - SIGRTMIN+28; - resp. syslog-or-kmsg - on SIGRTMIN+29), as + journal-or-kmsg (or + console on + SIGRTMIN+27, + kmsg on + SIGRTMIN+28), as controlled via systemd.log_target=journal-or-kmsg - (resp. systemd.log_target=console - on SIGRTMIN+27; - resp. systemd.log_target=kmsg - on SIGRTMIN+28; - resp - systemd.log_target=syslog-or-kmsg - on SIGRTMIN+29) on - the kernel command + (or + systemd.log_target=console + on SIGRTMIN+27 or + systemd.log_target=kmsg + on SIGRTMIN+28) + on the kernel command line. @@ -861,7 +865,7 @@ Environment - + $SYSTEMD_LOG_LEVEL systemd reads the @@ -971,7 +975,7 @@ /proc/cmdline instead.: - + systemd.unit= rd.systemd.unit= @@ -986,9 +990,9 @@ systemd.special7 for details about these units. The option prefixed with - rd. is honoured + rd. is honored only in the initial RAM disk (initrd), - while the one that isn't prefixed only + while the one that is not prefixed only in the main system. @@ -996,9 +1000,9 @@ systemd.dump_core= Takes a boolean - argument. If + argument. If , systemd dumps core when it - crashes. Otherwise no core dump is + crashes. Otherwise, no core dump is created. Defaults to . @@ -1007,9 +1011,9 @@ systemd.crash_shell= Takes a boolean - argument. If + argument. If , systemd spawns a shell when it - crashes. Otherwise no shell is + crashes. Otherwise, no shell is spawned. Defaults to , for security reasons, as the shell is not protected @@ -1024,14 +1028,14 @@ argument. If positive systemd activates the specified virtual terminal when it crashes. Defaults to - -1. + -1. systemd.confirm_spawn= Takes a boolean - argument. If + argument. If , asks for confirmation when spawning processes. Defaults to . @@ -1041,14 +1045,20 @@ systemd.show_status= Takes a boolean - argument. If - shows terse service status updates on - the console during bootup. Defaults to + argument or the constant + auto. If + , shows terse + service status updates on the console + during bootup. + auto behaves like + until a service + fails or there is a significant delay + in boot. Defaults to , unless is passed as kernel command line option in which case it defaults to - . + auto. @@ -1067,56 +1077,67 @@ systemd.default_standard_output= systemd.default_standard_error= Controls default - standard output/error output for + standard output and error output for services, with the same effect as the - resp. + and command line arguments described - above. + above, respectively. systemd.setenv= Takes a string - argument in the form - VARIABLE=VALUE. May be used to set - environment variables for the init - process and all its children at boot - time. May be used more than once to - set multiple variables. If the equal - sign and variable are missing unsets - an environment variable which might be - passed in from the initial ram - disk. + argument in the form VARIABLE=VALUE. + May be used to set default environment + variables to add to forked child processes. + May be used more than once to set multiple + variables. quiet - If passed turns off + Turn off status output at boot, much like systemd.show_status=false would. Note that this option is also read by the kernel itself and disables - kernel log output to the - kernel. Passing this option hence - turns off the usual output from both - the system manager and the + kernel log output. Passing this option + hence turns off the usual output from + both the system manager and the kernel. + + + + + debug + + Turn on debugging + output. This is equivalent to + systemd.log_level=debug. + Note that this option is also read by + the kernel itself and enables kernel + debug output. Passing this option + hence turns on the debug output from + both the system manager and the kernel. emergency + -b Boot into emergency mode. This is equivalent to systemd.unit=emergency.target - and provided for compatibility - reasons and to be easier to type. + and provided for compatibility reasons + and to be easier to + type. + rescue single s S @@ -1137,12 +1158,12 @@ 5 Boot into the - specified legacy SysV runlevel. This - is equivalent to + specified legacy SysV runlevel. These + are equivalent to systemd.unit=runlevel2.target, systemd.unit=runlevel3.target, systemd.unit=runlevel4.target, - resp. systemd.unit=runlevel5.target + and systemd.unit=runlevel5.target, respectively, and provided for compatibility reasons and to be easier to type. @@ -1190,7 +1211,7 @@ Daemon status notification socket. This is an - AF_UNIX datagram socket and is used to + AF_UNIX datagram socket and is used to implement the daemon notification logic as implemented by sd_notify3. @@ -1203,7 +1224,7 @@ Used internally by the shutdown8 tool to implement delayed - shutdowns. This is an AF_UNIX datagram + shutdowns. This is an AF_UNIX datagram socket. @@ -1214,7 +1235,7 @@ communication channel between systemctl1 and the systemd process. This is an - AF_UNIX stream socket. This interface + AF_UNIX stream socket. This interface is private to systemd and should not be used in external projects. @@ -1238,18 +1259,20 @@ See Also - systemd.conf5, + The systemd Homepage, + systemd-system.conf5, locale.conf5, systemctl1, - systemadm1, + journalctl1, systemd-notify1, daemon7, sd-daemon3, systemd.unit5, systemd.special5, - pkg-config1, + pkg-config1, kernel-command-line7, - bootup7 + bootup7, + systemd.directives7