X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.xml;h=f434bfcc580bcebc2e33ded102d5a364c8d265c9;hb=49d50c55bb78849f25bdf46fa76da5a6bdc5571f;hp=6edce4996a99ba76cb5f6bc03c70436954518d41;hpb=5dc50792ac1bc627bf9b50d259b4e7546b3f8d86;p=elogind.git diff --git a/man/systemd.xml b/man/systemd.xml index 6edce4996..f434bfcc5 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -141,14 +141,20 @@ Tell systemd to run a system instance (resp. session 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 + . @@ -256,7 +262,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 +323,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 +336,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 +361,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 @@ -388,7 +394,7 @@ track of processes. Control group information is maintained in the kernel, and is accessible via the file system hierarchy (beneath - /cgroup/systemd/), or in tools + /sys/fs/cgroup/systemd/), or in tools such as ps1 (ps xawf -eo pid,user,cgroup,args @@ -440,6 +446,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. @@ -840,8 +851,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