X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.xml;h=e74d71b126f096a2fd78c404f8e271841ec97da1;hb=92abbefbefb0adafb6714c8d8f9d25bc8280a2f7;hp=ba775c5c91197c902639ad46f2f86e34b55ffd1e;hpb=f3e219a238c716ffa06fab7b0618197c090dfd5a;p=elogind.git
diff --git a/man/systemd.xml b/man/systemd.xml
index ba775c5c9..e74d71b12 100644
--- a/man/systemd.xml
+++ b/man/systemd.xml
@@ -117,7 +117,7 @@
Extract D-Bus
interface introspection data. This is
- mostly useful at build at install time
+ mostly useful at install time
to generate data suitable for the
D-Bus interfaces
repository. Optionally the interface
@@ -135,17 +135,19 @@
default.target.
-
+
+
- Tell systemd to run in
- a particular mode. Argument is one of
- ,
- . Normally it
- should not be necessary to pass this
- option, as systemd automatically
- detects the mode it is started
- in. This call is hence of little use
- except for
+ Tell systemd to run a
+ system instance (resp. session
+ instance), even if the process ID is
+ not 1 (resp. is 1), i.e. system 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.
@@ -232,7 +234,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:
@@ -278,7 +280,7 @@
systemd units, which later may be restored by
activating the saved snapshot unit. For more
information see
- systemd.automount5.
+ systemd.snapshot5.
Timer units are useful for
triggering activation of other units based on
@@ -291,7 +293,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 +305,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 +320,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.
@@ -466,7 +468,7 @@
when figuring out whether a service
shall be enabled. Note that a service
unit with a native unit configuration
- file can be started by activating it
+ file cannot be started by activating it
in the SysV runlevel link
farm.