X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=man%2Fsystemctl.xml;h=42dd667aa9a59e152eacf33e62a07cdc2e93d607;hb=132b63bd3131bc72b92adfcfa434fc2ed8648487;hp=3d03c0374b3376b4ae34fcfe3b4c8dcedb400e5e;hpb=93651582aef1ee626dc6f8d032195acd73bc9372;p=thirdparty%2Fsystemd.git
diff --git a/man/systemctl.xml b/man/systemctl.xml
index 3d03c0374b3..42dd667aa9a 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -188,13 +188,15 @@ Sun 2017-02-26 20:57:49 EST 2h 3min left Sun 2017-02-26 11:56:36 EST 6h ago
statusPATTERNâ¦|PIDâ¦]
- Show terse runtime status information about one or
- more units, followed by most recent log data from the
- journal. If no units are specified, show system status. If
- combined with , also show the status of
- all units (subject to limitations specified with
- ). If a PID is passed, show information
- about the unit the process belongs to.
+ Show runtime status information about the whole system or about one or more units followed
+ by most recent log data from the journal. If no positional arguments are specified, and no unit
+ filter is given with , , or
+ , shows the status of the whole system. If combined with
+ , follows that with the status of all units. If positional arguments are
+ specified, each positional argument is treated as either a unit name to show, or a glob pattern
+ to show units whose names match that pattern, or a PID to show the unit containing that PID. When
+ , , or are used, units
+ are additionally filtered by the TYPE and ACTIVE state.This function is intended to generate human-readable
output. If you are looking for computer-parsable output,
@@ -237,29 +239,31 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: Current Time Service could not be
Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output error (5)
- The dot ("â") uses color on supported terminals to summarize the unit state at a glance. Along with
- its color, its shape varies according to its state: inactive or
- maintenance is a white circle ("â"), active is a green dot ("â"),
- deactivating is a white dot, failed or error is
- a red cross ("Ã"), and reloading is a green clockwise circle arrow ("â»").
-
-
- The "Loaded:" line in the output will show loaded if the unit has been loaded into
- memory. Other possible values for "Loaded:" include: error if there was a problem
- loading it, not-found if no unit file was found for this unit,
- bad-setting if an essential unit file setting could not be parsed and
- masked if the unit file has been masked. Along with showing the path to the unit file,
- this line will also show the enablement state. Enabled commands start at boot. See the full table of
- possible enablement states â including the definition of masked â in the documentation
- for the is-enabled command.
+ The dot ("â") uses color on supported terminals to summarize the unit state at a
+ glance. Along with its color, its shape varies according to its state:
+ inactive or maintenance is a white circle ("â"),
+ active is a green dot ("â"), deactivating is a white dot,
+ failed or error is a red cross ("Ã"), and
+ reloading is a green clockwise circle arrow ("â»").
+
+ The "Loaded:" line in the output will show loaded if the unit has been
+ loaded into memory. Other possible values for "Loaded:" include: error if
+ there was a problem loading it, not-found if no unit file was found for this
+ unit, bad-setting if an essential unit file setting could not be parsed and
+ masked if the unit file has been masked. Along with showing the path to the
+ unit file, this line will also show the enablement state. Enabled units are included in the
+ dependency network between units, and thus are started at boot or via some other form of
+ activation. See the full table of possible enablement states â including the definition of
+ masked â in the documentation for the is-enabled command.
The "Active:" line shows active state. The value is usually active or
- inactive. Active could mean started, bound, plugged in, etc depending on the unit type.
- The unit could also be in process of changing states, reporting a state of activating or
- deactivating. A special failed state is entered when the service
- failed in some way, such as a crash, exiting with an error code or timing out. If the failed state is
- entered the cause will be logged for later reference.
+ inactive. Active could mean started, bound, plugged in, etc depending on the
+ unit type. The unit could also be in process of changing states, reporting a state of
+ activating or deactivating. A special
+ failed state is entered when the service failed in some way, such as a crash,
+ exiting with an error code or timing out. If the failed state is entered the cause will be logged
+ for later reference.
@@ -1621,18 +1625,13 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
- The argument should be a comma-separated list of unit
- types such as and
- .
-
+ The argument is a comma-separated list of unit types such as and
+ . When units are listed with list-units,
+ show, or status, only units of the specified types will be
+ shown. By default, units of all types are shown.
- If one of the arguments is a unit type, when listing
- units, limit display to certain unit types. Otherwise, units
- of all types will be shown.
-
- As a special case, if one of the arguments is
- , a list of allowed values will be
- printed and the program will exit.
+ As a special case, if one of the arguments is , a list of allowed values
+ will be printed and the program will exit.
@@ -1640,14 +1639,13 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
- The argument should be a comma-separated list of unit
- LOAD, SUB, or ACTIVE states. When listing units, show only
- those in the specified states. Use
- to show only failed units.
-
- As a special case, if one of the arguments is
- , a list of allowed values will be
- printed and the program will exit.
+ The argument is a comma-separated list of unit LOAD, SUB, or ACTIVE states. When listing
+ units with list-units, show, or status,
+ show only those in the specified states. Use or
+ to show only failed units.
+
+ As a special case, if one of the arguments is , a list of allowed values
+ will be printed and the program will exit.
@@ -1928,23 +1926,21 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
- When system shutdown or sleep state is request, this option controls how to deal with
- inhibitor locks. It takes one of auto, yes or
+ When system shutdown or sleep state is requested, this option controls checking of inhibitor
+ locks. It takes one of auto, yes or
no. Defaults to auto, which will behave like
- yes for interactive invocations (i.e. from a TTY) and no
- for non-interactive invocations.
- yes will let the request respect inhibitor locks.
- no will let the request ignore inhibitor locks.
-
- Applications can establish inhibitor locks to avoid that certain important operations
- (such as CD burning or suchlike) are interrupted by system shutdown or a sleep state. Any user may
- take these locks and privileged users may override these locks.
- If any locks are taken, shutdown and sleep state requests will normally fail (unless privileged)
- and a list of active locks is printed.
- However, if no is specified or auto is specified on a
- non-interactive requests, the established locks are ignored and not shown, and the operation
- attempted anyway, possibly requiring additional privileges.
- May be overridden by .
+ yes for interactive invocations (i.e. from a TTY) and no for
+ non-interactive invocations. yes lets the request respect inhibitor locks.
+ no lets the request ignore inhibitor locks.
+
+ Applications can establish inhibitor locks to prevent certain important operations (such as
+ CD burning) from being interrupted by system shutdown or sleep. Any user may take these locks and
+ privileged users may override these locks. If any locks are taken, shutdown and sleep state
+ requests will normally fail (unless privileged). However, if no is specified or
+ auto is specified on a non-interactive requests, the operation will be
+ attempted. If locks are present, the operation may require additional privileges.
+
+ Option provides another way to override inhibitors.