X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.xml;h=0798f231b93e84df1413924c677d26da20e12ffc;hp=4f4a588a98e677e306dbe4313c19d3abb2b618a5;hb=1e001f52d20a4685c9e8cf3cfa690021ca05c9e7;hpb=ad678a066b4ba5d8914dd7d5a4093572841205cf diff --git a/man/systemd.xml b/man/systemd.xml index 4f4a588a9..0798f231b 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -232,7 +232,7 @@ configuration or dynamically from system state. Units may be active (meaning started, bound, plugged in, ... depending on the unit type), or inactive (meaning - stopped, unbound, unplugged, ...), as well is in the + stopped, unbound, unplugged, ...), as well as in the process of being activated or deactivated, i.e. between the two states. The following unit types are available: @@ -291,7 +291,7 @@ systemd. They are described in systemd.swap5. Path units may be used - activate other services when file system + to activate other services when file system objects change or are modified. See systemd.path5. @@ -303,7 +303,7 @@ systemd.special7. On boot systemd activates the target unit - default.target whose job it is to + default.target whose job is to activate on-boot services and other on-boot units by pulling them in via dependencies. Usually the unit name is just an alias (symlink) for either @@ -318,7 +318,7 @@ systemd.special7 for details about these target units. - Processes systemd spawns ared placed in + Processes systemd spawns are placed in individual Linux control groups named after the unit which they belong to in the private systemd hierarchy. (see /dev/initctl interface is - provided, and comaptibility implementations of the - various SysV client tools available. In addition to - that various established Unix functionality such as + provided, and compatibility implementations of the + various SysV client tools are available. In addition to + that, various established Unix functionality such as /etc/fstab or the utmp database are supported.