X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.xml;h=c6c06e57e9fd1ebcc5938ecd2e8eae2199196a53;hp=edd824d31d4ff41fd95ac31290d81576f7004f5c;hb=b24a167b6f0f9a44686736734e6d0cec07e1efa3;hpb=77d5f105bf63330350c7bddacdeda914f945590f diff --git a/man/systemd.xml b/man/systemd.xml index edd824d31..c6c06e57e 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -45,7 +45,7 @@ systemd init - systemd System and Session Manager + systemd System and Service Manager @@ -60,7 +60,7 @@ Description - systemd is a system and session manager for + systemd is a system and service manager for Linux operating systems. When run as first process on boot (as PID 1), it acts as init system that brings up and maintains userspace services. @@ -77,7 +77,7 @@ When run as system instance, systemd interprets the configuration file system.conf, otherwise - session.conf. See + user.conf. See systemd.conf5 for more information. @@ -136,44 +136,59 @@ - + Tell systemd to run a - system instance (resp. session + 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. + not 1 (resp. is 1), i.e. systemd is + not (resp. is) run as init process. Normally it should not be necessary to pass these options, as systemd automatically detects the mode it is started in. These options are hence of - little use except for - debugging. + little use except for debugging. Note + that it is not supported booting and + maintaining a full system with systemd + running in + mode, but PID not 1. In practice, + passing explicitly is + only useful in conjunction with + . - Dump core on crash. This switch has no effect when run as session instance. + Dump core on + crash. This switch has no effect when + run as user + instance. - Run shell on crash. This switch has no effect when run as session instance. + Run shell on + crash. This switch has no effect when + run as user + instance. - Ask for confirmation when spawning processes. This switch has no effect when run as session instance. + Ask for confirmation + when spawning processes. This switch + has no effect when run as user + instance. Show terse service status information while booting. This - switch has no effect when run as - session instance. Takes a boolean - argument which may be omitted - which is interpreted as + switch has no effect when run as user + instance. Takes a boolean argument + which may be omitted which is + interpreted as . @@ -182,7 +197,7 @@ Controls whether output of SysV init scripts will be directed to the console. This switch - has no effect when run as session + has no effect when run as user instance. Takes a boolean argument which may be omitted which is interpreted as @@ -256,7 +271,7 @@ 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 - 'maintenance' state is available as well which is very + '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 @@ -317,9 +332,9 @@ systemd.timer5. Swap units are very similar to - mount units and encapsulated memory swap + mount units and encapsulate memory swap partitions or files of the operating - systemd. They are described in systemd.swap5. + system. They are described in systemd.swap5. Path units may be used to activate other services when file system @@ -330,7 +345,7 @@ Units are named as their configuration files. Some units have special semantics. A detailed - list you may find in + list is available in systemd.special7. systemd knows various kinds of dependencies, @@ -355,7 +370,7 @@ this. Application programs and units (via - dependencies) may requests state changes of units. In + dependencies) may request state changes of units. In systemd, these requests are encapsulated as 'jobs' and maintained in a job queue. Jobs may succeed or can fail, their execution is ordered based on the ordering @@ -440,6 +455,11 @@ ideas behind systemd please refer to the Original Design Document. + + Note that some but not all interfaces provided + by systemd are covered by the Interface + Stability Promise. @@ -478,10 +498,10 @@ - Session unit directories + User unit directories Similar rules apply - for the session unit + for the user unit directories. However, here the XDG Base Directory specification @@ -489,11 +509,11 @@ units. Applications should place their unit files in the directory returned by pkg-config systemd - --variable=systemdsessionunitdir. Global + --variable=systemduserunitdir. Global configuration is done in the directory reported by pkg-config systemd - --variable=systemdsessionconfdir. The + --variable=systemduserconfdir. The enable and disable commands of the @@ -554,12 +574,12 @@ to systemctl daemon-reexec. - systemd session managers will + systemd user managers will start the exit.target unit when this signal is received. This is mostly equivalent to - systemctl --session start + systemctl --user start exit.target. @@ -574,7 +594,7 @@ systemctl start ctl-alt-del.target. - systemd session managers + systemd user managers treat this signal the same way as SIGTERM. @@ -591,7 +611,7 @@ kbrequest.target. This signal is ignored by - systemd session + systemd user managers. @@ -746,7 +766,7 @@ $XDG_DATA_HOME $XDG_DATA_DIRS - The systemd session + The systemd user manager uses these variables in accordance to the XDG @@ -840,8 +860,8 @@ Takes a boolean argument. If systemd spawns a shell when it - crashes. Otherwise no core dump is - created. Defaults to + crashes. Otherwise no shell is + spawned. Defaults to , for security reasons, as the shell is not protected by any password