X-Git-Url: http://git.ipfire.org/?p=thirdparty%2Fsystemd.git;a=blobdiff_plain;f=man%2Fsystemd.service.xml;h=fbb2987d0bec705a8c45255d1c04903b3ffb7d67;hp=a4a49f39af2ecf6e64d45ae91730bf3015fd2228;hb=c53da7ed02a5d732c9449f79c19675b90a6032e3;hpb=57b611a5bf7e227498c19e6a09c2d2dbe8c24863
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index a4a49f39af2..fbb2987d0be 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -35,9 +35,9 @@
systemd.unit5
for the common options of all unit configuration files. The common
configuration items are configured in the generic
- [Unit] and [Install]
+ [Unit] and [Install]
sections. The service specific configuration options are
- configured in the [Service] section.
+ configured in the [Service] section.
Additional options are listed in
systemd.exec5,
@@ -138,7 +138,7 @@
Options
- Service files must include a [Service]
+ Service files must include a [Service]
section, which carries information about the service and the
process it supervises. A number of options that may be used in
this section are shared with other unit types. These options are
@@ -147,7 +147,7 @@
systemd.kill5
and
systemd.resource-control5.
- The options specific to the [Service] section
+ The options specific to the [Service] section
of service units are the following:
@@ -217,7 +217,7 @@
this notification message has been sent. If this option is used, NotifyAccess= (see
below) should be set to open access to the notification socket provided by systemd. If
NotifyAccess= is missing or set to , it will be forcibly set to
- .
+ .Behavior of is very similar to ; however,
actual execution of the service program is delayed until all active jobs are dispatched. This may be used
@@ -884,7 +884,7 @@
project='man-pages'>signal7 for
a list of signal names.
- Note that this setting does not change the the mapping between numeric exit statuses and their
+ Note that this setting does not change the mapping between numeric exit statuses and their
names, i.e. regardless how this setting is used 0 will still be mapped to SUCCESS
(and thus typically shown as 0/SUCCESS in tool outputs) and 1 to
FAILURE (and thus typically shown as 1/FAILURE), and so on. It
@@ -896,12 +896,12 @@
this option will have no effect.
- A service with with the SuccessExitStatus= setting
+ A service with the SuccessExitStatus= settingSuccessExitStatus=TEMPFAIL 250 SIGUSR1Exit status 75 (TEMPFAIL), 250, and the termination signal
- SIGKILL are considered clean service terminations.
+ SIGUSR1 are considered clean service terminations.Note: systemd-analyze exit-status may be used to list exit statuses and
@@ -1078,8 +1078,8 @@
manager. If set to kill and one of the service's processes is killed by the OOM
killer the kernel is instructed to kill all remaining processes of the service, too. Defaults to the
setting DefaultOOMPolicy= in
- system.conf5 is
- set to, except for services where Delegate= is turned on, where it defaults to
+ systemd-system.conf5
+ is set to, except for services where Delegate= is turned on, where it defaults to
continue.Use the OOMScoreAdjust= setting to configure whether processes of the unit
@@ -1495,7 +1495,7 @@ ExecStart=/usr/sbin/simple-dbus-service
WantedBy=multi-user.target
For bus-activatable services, do not
- include a [Install] section in the systemd
+ include a [Install] section in the systemd
service file, but use the SystemdService=
option in the corresponding DBus service file, for example
(/usr/share/dbus-1/system-services/org.example.simple-dbus-service.service):