diff --git a/man/systemctl.xml b/man/systemctl.xml
index 04b2e9813d..dfaca638c2 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -501,10 +501,11 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
kill PATTERN…
- Send a signal to one or more processes of the
- unit. Use to select which
- process to kill. Use to select
- the signal to send.
+ Send a UNIX process signal to one or more processes of the unit. Use
+ to select which process to send the signal to. Use
+ to select the signal to send. Combine with
+ to enqueue a POSIX Realtime Signal with an associated
+ value.
@@ -2124,40 +2125,46 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
- When used with kill, choose which
- processes to send a signal to. Must be one of
- , or
- to select whether to kill only the main
- process, the control process or all processes of the
- unit. The main process of the unit is the one that defines
- the life-time of it. A control process of a unit is one that
- is invoked by the manager to induce state changes of it. For
- example, all processes started due to the
- ExecStartPre=,
- ExecStop= or
- ExecReload= settings of service units are
- control processes. Note that there is only one control
- process per unit at a time, as only one state change is
- executed at a time. For services of type
- Type=forking, the initial process started
- by the manager for ExecStart= is a
- control process, while the process ultimately forked off by
- that one is then considered the main process of the unit (if
- it can be determined). This is different for service units
- of other types, where the process forked off by the manager
- for ExecStart= is always the main process
- itself. A service unit consists of zero or one main process,
- zero or one control process plus any number of additional
- processes. Not all unit types manage processes of these
- types however. For example, for mount units, control processes
- are defined (which are the invocations of
- &MOUNT_PATH; and
- &UMOUNT_PATH;), but no main process
- is defined. If omitted, defaults to
+ When used with kill, choose which processes to send a UNIX process signal
+ to. Must be one of , or to
+ select whether to kill only the main process, the control process or all processes of the unit. The
+ main process of the unit is the one that defines the life-time of it. A control process of a unit
+ is one that is invoked by the manager to induce state changes of it. For example, all processes
+ started due to the ExecStartPre=, ExecStop= or
+ ExecReload= settings of service units are control processes. Note that there is
+ only one control process per unit at a time, as only one state change is executed at a time. For
+ services of type Type=forking, the initial process started by the manager for
+ ExecStart= is a control process, while the process ultimately forked off by that
+ one is then considered the main process of the unit (if it can be determined). This is different
+ for service units of other types, where the process forked off by the manager for
+ ExecStart= is always the main process itself. A service unit consists of zero or
+ one main process, zero or one control process plus any number of additional processes. Not all unit
+ types manage processes of these types however. For example, for mount units, control processes are
+ defined (which are the invocations of &MOUNT_PATH; and
+ &UMOUNT_PATH;), but no main process is defined. If omitted, defaults to
.
+
+ INT
+
+ If used with the kill command, enqueues a signal along with the
+ specified integer value parameter to the specified process(es). This operation is only available for
+ POSIX Realtime Signals (i.e. or
+ ), and ensures the signals are generated via the sigqueue3
+ system call, rather than kill3. The
+ specified value must be a 32bit signed integer, and may be specified either in decimal, in
+ hexademical (if prefixed with 0x), octal (if prefixed with 0o)
+ or binary (if prefixed with 0b)
+
+ If this option is used the signal will only be enqueued on the control or main process of the
+ unit, never on other processes belonging to the unit, i.e. will only
+ affect main and control processes but no other processes.
+
+