Linux.pl: Przeglądarka stron manuala

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

NAME
systemctl - Control the systemd system and service manager

SYNOPSIS
systemctl [OPTIONS...] COMMAND [UNIT...]

DESCRIPTION
systemctl may be used to introspect and control the state of the
"systemd" system and service manager. Please refer to systemd(1) for an
introduction into the basic concepts and functionality this tool
manages.

COMMANDS
The following commands are understood:

Unit Commands (Introspection and Modification)
list-units [PATTERN...]
List units that systemd currently has in memory. This includes
units that are either referenced directly or through a dependency,
units that are pinned by applications programmatically, or units
that were active in the past and have failed. By default only units
which are active, have pending jobs, or have failed are shown; this
can be changed with option --all. If one or more PATTERNs are
specified, only units matching one of them are shown. The units
that are shown are additionally filtered by --type= and --state= if
those options are specified.

Note that this command does not show unit templates, but only
instances of unit templates. Units templates that aren't
instantiated are not runnable, and will thus never show up in the
output of this command. Specifically this means that foo@.service
will never be shown in this list -- unless instantiated, e.g. as
foo@bar.service. Use list-unit-files (see below) for listing
installed unit template files.

Produces output similar to

UNIT LOAD ACTIVE SUB DESCRIPTION
sys-module-fuse.device loaded active plugged /sys/module/fuse
-.mount loaded active mounted Root Mount
boot-efi.mount loaded active mounted /boot/efi
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
user@1000.service loaded failed failed User Manager for UID 1000
...
systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

123 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The header and the last unit of a given type are underlined if the
terminal supports that. A colored dot is shown next to services
which were masked, not found, or otherwise failed.

The LOAD column shows the load state, one of loaded, not-found,
bad-setting, error, masked. The ACTIVE columns shows the general
unit state, one of the following:

systemctl --state=help

command may be used to display the current set of possible values.

This is the default command.

list-automounts [PATTERN...]
List automount units currently in memory, ordered by mount path. If
one or more PATTERNs are specified, only automount units matching
one of them are shown. Produces output similar to

WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
/dev/sdb1 /mnt/test no 120s mnt-test.automount
binfmt_misc /proc/sys/fs/binfmt_misc yes 0 proc-sys-fs-binfmt_misc.automount

2 automounts listed.

Also see --show-types, --all, and --state=.

list-sockets [PATTERN...]
List socket units currently in memory, ordered by listening
address. If one or more PATTERNs are specified, only socket units
matching one of them are shown. Produces output similar to

LISTEN UNIT ACTIVATES
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
/dev/rfkill systemd-rfkill.socket systemd-rfkill.service
...

5 sockets listed.

Note: because the addresses might contains spaces, this output is
not suitable for programmatic consumption.

Also see --show-types, --all, and --state=.

list-timers [PATTERN...]
List timer units currently in memory, ordered by the time they
elapse next. If one or more PATTERNs are specified, only units
matching one of them are shown. Produces output similar to

NEXT LEFT LAST PASSED UNIT ACTIVATES
- - Thu 2017-02-23 13:40:29 EST 3 days ago ureadahead-stop.timer ureadahead-stop.service
Sun 2017-02-26 18:55:42 EST 1min 14s left Thu 2017-02-23 13:54:44 EST 3 days ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
Sun 2017-02-26 20:37:16 EST 1h 42min left Sun 2017-02-26 11:56:36 EST 6h ago apt-daily.timer apt-daily.service
Sun 2017-02-26 20:57:49 EST 2h 3min left Sun 2017-02-26 11:56:36 EST 6h ago snapd.refresh.timer snapd.refresh.service

NEXT shows the next time the timer will run.

LEFT shows how long till the next time the timer runs.

LAST shows the last time the timer ran.

PASSED shows how long has passed since the timer last ran.

UNIT shows the name of the timer

ACTIVATES shows the name the service the timer activates when it
runs.

Also see --all and --state'

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

NAME
systemctl - Control the systemd system and service manager

SYNOPSIS
systemctl [OPTIONS...] COMMAND [UNIT...]

COMMANDS
The following commands are understood:

Produces output similar to

123 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The header and the last unit of a given type are underlined if the
terminal supports that. A colored dot is shown next to services
which were masked, not found, or otherwise failed.

The LOAD column shows the load state, one of loaded, not-found,
bad-setting, error, masked. The ACTIVE columns shows the general
unit state, one of the following:

systemctl --state=help

command may be used to display the current set of possible values.

This is the default command.

WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
/dev/sdb1 /mnt/test no 120s mnt-test.automount
binfmt_misc /proc/sys/fs/binfmt_misc yes 0 proc-sys-fs-binfmt_misc.automount

2 automounts listed.

Also see --show-types, --all, and --state=.

LISTEN UNIT ACTIVATES
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
/dev/rfkill systemd-rfkill.socket systemd-rfkill.service
...

5 sockets listed.

Note: because the addresses might contains spaces, this output is
not suitable for programmatic consumption.

Also see --show-types, --all, and --state=.

NEXT shows the next time the timer will run.

LEFT shows how long till the next time the timer runs.

LAST shows the last time the timer ran.

PASSED shows how long has passed since the timer last ran.

UNIT shows the name of the timer

ACTIVATES shows the name the service the timer activates when it
runs.

Also see --all and --state'

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

NAME
systemctl - Control the systemd system and service manager

SYNOPSIS
systemctl [OPTIONS...] COMMAND [UNIT...]

COMMANDS
The following commands are understood:

Produces output similar to

123 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The header and the last unit of a given type are underlined if the
terminal supports that. A colored dot is shown next to services
which were masked, not found, or otherwise failed.

The LOAD column shows the load state, one of loaded, not-found,
bad-setting, error, masked. The ACTIVE columns shows the general
unit state, one of the following:

systemctl --state=help

command may be used to display the current set of possible values.

This is the default command.

WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
/dev/sdb1 /mnt/test no 120s mnt-test.automount
binfmt_misc /proc/sys/fs/binfmt_misc yes 0 proc-sys-fs-binfmt_misc.automount

2 automounts listed.

Also see --show-types, --all, and --state=.

LISTEN UNIT ACTIVATES
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
/dev/rfkill systemd-rfkill.socket systemd-rfkill.service
...

5 sockets listed.

Note: because the addresses might contains spaces, this output is
not suitable for programmatic consumption.

Also see --show-types, --all, and --state=.

NEXT shows the next time the timer will run.

LEFT shows how long till the next time the timer runs.

LAST shows the last time the timer ran.

PASSED shows how long has passed since the timer last ran.

UNIT shows the name of the timer

ACTIVATES shows the name the service the timer activates when it
runs.

Also see --all and --state'

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

NAME
systemctl - Control the systemd system and service manager

SYNOPSIS
systemctl [OPTIONS...] COMMAND [UNIT...]

COMMANDS
The following commands are understood:

Produces output similar to

123 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The header and the last unit of a given type are underlined if the
terminal supports that. A colored dot is shown next to services
which were masked, not found, or otherwise failed.

The LOAD column shows the load state, one of loaded, not-found,
bad-setting, error, masked. The ACTIVE columns shows the general
unit state, one of the following:

systemctl --state=help

command may be used to display the current set of possible values.

This is the default command.

WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
/dev/sdb1 /mnt/test no 120s mnt-test.automount
binfmt_misc /proc/sys/fs/binfmt_misc yes 0 proc-sys-fs-binfmt_misc.automount

2 automounts listed.

Also see --show-types, --all, and --state=.

LISTEN UNIT ACTIVATES
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
/dev/rfkill systemd-rfkill.socket systemd-rfkill.service
...

5 sockets listed.

Note: because the addresses might contains spaces, this output is
not suitable for programmatic consumption.

Also see --show-types, --all, and --state=.

NEXT shows the next time the timer will run.

LEFT shows how long till the next time the timer runs.

LAST shows the last time the timer ran.

PASSED shows how long has passed since the timer last ran.

UNIT shows the name of the timer

ACTIVATES shows the name the service the timer activates when it
runs.

Also see --all and --state'

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

NAME
systemctl - Control the systemd system and service manager

SYNOPSIS
systemctl [OPTIONS...] COMMAND [UNIT...]

COMMANDS
The following commands are understood:

Produces output similar to

123 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The header and the last unit of a given type are underlined if the
terminal supports that. A colored dot is shown next to services
which were masked, not found, or otherwise failed.

The LOAD column shows the load state, one of loaded, not-found,
bad-setting, error, masked. The ACTIVE columns shows the general
unit state, one of the following:

systemctl --state=help

command may be used to display the current set of possible values.

This is the default command.

WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
/dev/sdb1 /mnt/test no 120s mnt-test.automount
binfmt_misc /proc/sys/fs/binfmt_misc yes 0 proc-sys-fs-binfmt_misc.automount

2 automounts listed.

Also see --show-types, --all, and --state=.

LISTEN UNIT ACTIVATES
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
/dev/rfkill systemd-rfkill.socket systemd-rfkill.service
...

5 sockets listed.

Note: because the addresses might contains spaces, this output is
not suitable for programmatic consumption.

Also see --show-types, --all, and --state=.

NEXT shows the next time the timer will run.

LEFT shows how long till the next time the timer runs.

LAST shows the last time the timer ran.

PASSED shows how long has passed since the timer last ran.

UNIT shows the name of the timer

ACTIVATES shows the name the service the timer activates when it
runs.

Also see --all and --state'

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

NAME
systemctl - Control the systemd system and service manager

SYNOPSIS
systemctl [OPTIONS...] COMMAND [UNIT...]

COMMANDS
The following commands are understood:

Produces output similar to

123 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The header and the last unit of a given type are underlined if the
terminal supports that. A colored dot is shown next to services
which were masked, not found, or otherwise failed.

The LOAD column shows the load state, one of loaded, not-found,
bad-setting, error, masked. The ACTIVE columns shows the general
unit state, one of the following:

systemctl --state=help

command may be used to display the current set of possible values.

This is the default command.

WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
/dev/sdb1 /mnt/test no 120s mnt-test.automount
binfmt_misc /proc/sys/fs/binfmt_misc yes 0 proc-sys-fs-binfmt_misc.automount

2 automounts listed.

Also see --show-types, --all, and --state=.

LISTEN UNIT ACTIVATES
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
/dev/rfkill systemd-rfkill.socket systemd-rfkill.service
...

5 sockets listed.

Note: because the addresses might contains spaces, this output is
not suitable for programmatic consumption.

Also see --show-types, --all, and --state=.

NEXT shows the next time the timer will run.

LEFT shows how long till the next time the timer runs.

LAST shows the last time the timer ran.

PASSED shows how long has passed since the timer last ran.

UNIT shows the name of the timer

ACTIVATES shows the name the service the timer activates when it
runs.

Also see --all and --state'

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

NAME
systemctl - Control the systemd system and service manager

SYNOPSIS
systemctl [OPTIONS...] COMMAND [UNIT...]

COMMANDS
The following commands are understood:

Produces output similar to

123 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The header and the last unit of a given type are underlined if the
terminal supports that. A colored dot is shown next to services
which were masked, not found, or otherwise failed.

The LOAD column shows the load state, one of loaded, not-found,
bad-setting, error, masked. The ACTIVE columns shows the general
unit state, one of the following:

systemctl --state=help

command may be used to display the current set of possible values.

This is the default command.

WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
/dev/sdb1 /mnt/test no 120s mnt-test.automount
binfmt_misc /proc/sys/fs/binfmt_misc yes 0 proc-sys-fs-binfmt_misc.automount

2 automounts listed.

Also see --show-types, --all, and --state=.

LISTEN UNIT ACTIVATES
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
/dev/rfkill systemd-rfkill.socket systemd-rfkill.service
...

5 sockets listed.

Note: because the addresses might contains spaces, this output is
not suitable for programmatic consumption.

Also see --show-types, --all, and --state=.

NEXT shows the next time the timer will run.

LEFT shows how long till the next time the timer runs.

LAST shows the last time the timer ran.

PASSED shows how long has passed since the timer last ran.

UNIT shows the name of the timer

ACTIVATES shows the name the service the timer activates when it
runs.

Also see --all and --state'

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

NAME
systemctl - Control the systemd system and service manager

SYNOPSIS
systemctl [OPTIONS...] COMMAND [UNIT...]

COMMANDS
The following commands are understood:

Produces output similar to

123 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The header and the last unit of a given type are underlined if the
terminal supports that. A colored dot is shown next to services
which were masked, not found, or otherwise failed.

The LOAD column shows the load state, one of loaded, not-found,
bad-setting, error, masked. The ACTIVE columns shows the general
unit state, one of the following:

systemctl --state=help

command may be used to display the current set of possible values.

This is the default command.

WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
/dev/sdb1 /mnt/test no 120s mnt-test.automount
binfmt_misc /proc/sys/fs/binfmt_misc yes 0 proc-sys-fs-binfmt_misc.automount

2 automounts listed.

Also see --show-types, --all, and --state=.

LISTEN UNIT ACTIVATES
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
/dev/rfkill systemd-rfkill.socket systemd-rfkill.service
...

5 sockets listed.

Note: because the addresses might contains spaces, this output is
not suitable for programmatic consumption.

Also see --show-types, --all, and --state=.

NEXT shows the next time the timer will run.

LEFT shows how long till the next time the timer runs.

LAST shows the last time the timer ran.

PASSED shows how long has passed since the timer last ran.

UNIT shows the name of the timer

ACTIVATES shows the name the service the timer activates when it
runs.

Also see --all and --state'

SYSTEMCTL(1) systemctl SYSTEMCTL(1)

systemctl show will show all available properties, most of which
are derived or closely match the options described in systemd-
system.conf(5).

Properties for units vary by unit type, so showing any unit (even a
non-existent one) is a way to list properties pertaining to this
type. Similarly, showing any job will list properties pertaining to
all jobs. Properties for units are documented in systemd.unit(5),
and the pages for individual unit types systemd.service(5),
systemd.socket(5), etc.

-P
Equivalent to --value --property=, i.e. shows the value of the
property without the property name or "=". Note that using -P once
will also affect all properties listed with -p/--property=.

-a, --all
When listing units with list-units, also show inactive units and
units which are following other units. When showing
unit/job/manager properties, show all properties regardless whether
they are set or not.

To list all units installed in the file system, use the
list-unit-files command instead.

When listing units with list-dependencies, recursively show
dependencies of all dependent units (by default only dependencies
of target units are shown).

When used with status, show journal messages in full, even if they
include unprintable characters or are very long. By default, fields
with unprintable characters are abbreviated as "blob data". (Note
that the pager may escape unprintable characters again.)

-r, --recursive
When listing units, also show units of local containers. Units of
local containers will be prefixed with the container name,
separated by a single colon character (":").

--reverse
Show reverse dependencies between units with list-dependencies,
i.e. follow dependencies of type WantedBy=, RequiredBy=, PartOf=,
BoundBy=, instead of Wants= and similar.

--after
With list-dependencies, show the units that are ordered before the
specified unit. In other words, recursively list units following
the After= dependency.

Note that any After= dependency is automatically mirrored to create
a Before= dependency. Temporal dependencies may be specified
explicitly, but are also created implicitly for units which are
WantedBy= targets (see systemd.target(5)), and as a result of other
directives (for example RequiresMountsFor=). Both explicitly and
implicitly introduced dependencies are shown with
list-dependencies.

When passed to the list-jobs command, for each printed job show
which other jobs are waiting for it. May be combined with --before
to show both the jobs waiting for each job as well as all jobs each
job is waiting for.

--before
With list-dependencies, show the units that are ordered after the
specified unit. In other words, recursively list units following
the Before= dependency.

When passed to the list-jobs command, for each printed job show
which other jobs it is waiting for. May be combined with --after to
show both the jobs waiting for each job as well as all jobs each
job is waiting for.

--with-dependencies
When used with status, cat, list-units, and list-unit-files, those
commands print all specified units and the dependencies of those
units.

Options --reverse, --after, --before may be used to change what
types of dependencies are shown.

-l, --full
Do not ellipsize unit names, process tree entries, journal output,
or truncate unit descriptions in the output of status, list-units,
list-jobs, and list-timers.

Also, show installation targets in the output of is-enabled.

--value
When printing properties with show, only print the value, and skip
the property name and "=". Also see option -P above.

--show-types
When showing sockets, show the type of the socket.

--job-mode=
When queuing a new job, this option controls how to deal with
already queued jobs. It takes one of "fail", "replace",
"replace-irreversibly", "isolate", "ignore-dependencies",
"ignore-requirements", "flush", or "triggering". Defaults to
"replace", except when the isolate command is used which implies
the "isolate" job mode.

If "fail" is specified and a requested operation conflicts with a
pending job (more specifically: causes an already pending start job
to be reversed into a stop job or vice versa), cause the operation
to fail.

If "replace" (the default) is specified, any conflicting pending
job will be replaced, as necessary.

If "replace-irreversibly" is specified, operate like "replace", but
also mark the new jobs as irreversible. This prevents future
conflicting transactions from replacing these jobs (or even being
enqueued while the irreversible jobs are still pending).
Irreversible jobs can still be cancelled using the cancel command.
This job mode should be used on any transaction which pulls in
shutdown.target.

"isolate" is only valid for start operations and causes all other
units to be stopped when the specified unit is started. This mode
is always used when the isolate command is used.

"flush" will cause all queued jobs to be canceled when the new job
is enqueued.

If "ignore-dependencies" is specified, then all unit dependencies
are ignored for this new job and the operation is executed
immediately. If passed, no required units of the unit passed will
be pulled in, and no ordering dependencies will be honored. This is
mostly a debugging and rescue tool for the administrator and should
not be used by applications.

"ignore-requirements" is similar to "ignore-dependencies", but only
causes the requirement dependencies to be ignored, the ordering
dependencies will still be honored.

"triggering" may only be used with systemctl stop. In this mode,
the specified unit and any active units that trigger it are
stopped. See the discussion of Triggers= in systemd.unit(5) for
more information about triggering units.

-T, --show-transaction
When enqueuing a unit job (for example as effect of a systemctl
start invocation or similar), show brief information about all jobs
enqueued, covering both the requested job and any added because of
unit dependencies. Note that the output will only include jobs
immediately part of the transaction requested. It is possible that
service start-up program code run as effect of the enqueued jobs
might request further jobs to be pulled in. This means that
completion of the listed jobs might ultimately entail more jobs
than the listed ones.

--fail
Shorthand for --job-mode=fail.

When used with the kill command, if no units were killed, the
operation results in an error.

--check-inhibitors=
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" 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 --force provides another way to override inhibitors.

-i
Shortcut for --check-inhibitors=no.

--dry-run
Just print what would be done. Currently supported by verbs halt,
poweroff, reboot, kexec, suspend, hibernate, hybrid-sleep,
suspend-then-hibernate, default, rescue, emergency, and exit.

-q, --quiet
Suppress printing of the results of various commands and also the
hints about truncated log lines. This does not suppress output of
commands for which the printed output is the only result (like
show). Errors are always printed.

--no-block
Do not synchronously wait for the requested operation to finish. If
this is not specified, the job will be verified, enqueued and
systemctl will wait until the unit's start-up is completed. By
passing this argument, it is only verified and enqueued. This
option may not be combined with --wait.

--wait
Synchronously wait for started units to terminate again. This
option may not be combined with --no-block. Note that this will
wait forever if any given unit never terminates (by itself or by
getting stopped explicitly); particularly services which use
"RemainAfterExit=yes".

When used with is-system-running, wait until the boot process is
completed before returning.

--user
Talk to the service manager of the calling user, rather than the
service manager of the system.

--system
Talk to the service manager of the system. This is the implied
default.

--failed
List units in failed state. This is equivalent to --state=failed.

--no-wall
Do not send wall message before halt, power-off and reboot.

--global
When used with enable and disable, operate on the global user
configuration directory, thus enabling or disabling a unit file
globally for all future logins of all users.

--no-reload
When used with enable and disable, do not implicitly reload daemon
configuration after executing the changes.

--no-ask-password
When used with start and related commands, disables asking for
passwords. Background services may require input of a password or
passphrase string, for example to unlock system hard disks or
cryptographic certificates. Unless this option is specified and the
command is invoked from a terminal, systemctl will query the user
on the terminal for the necessary secrets. Use this option to
switch this behavior off. In this case, the password must be
supplied by some other means (for example graphical password
agents) or the service might fail. This also disables querying the
user for authentication for privileged operations.

--kill-whom=
When used with kill, choose which processes to send a signal to.
Must be one of main, control or all 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 /bin/mount and /bin/umount),
but no main process is defined. If omitted, defaults to all.

-s, --signal=
When used with kill, choose which signal to send to selected
processes. Must be one of the well-known signal specifiers such as
SIGTERM, SIGINT or SIGSTOP. If omitted, defaults to SIGTERM.

The special value "help" will list the known values and the program
will exit immediately, and the special value "list" will list known
values along with the numerical signal numbers and the program will
exit immediately.

--what=
Select what type of per-unit resources to remove when the clean
command is invoked, see below. Takes one of configuration, state,
cache, logs, runtime to select the type of resource. This option
may be specified more than once, in which case all specified
resource types are removed. Also accepts the special value all as a
shortcut for specifying all five resource types. If this option is
not specified defaults to the combination of cache and runtime,
i.e. the two kinds of resources that are generally considered to be
redundant and can be reconstructed on next invocation.

-f, --force
When used with enable, overwrite any existing conflicting symlinks.

When used with edit, create all of the specified units which do not
already exist.

When used with halt, poweroff, reboot or kexec, execute the
selected operation without shutting down all units. However, all
processes will be killed forcibly and all file systems are
unmounted or remounted read-only. This is hence a drastic but
relatively safe option to request an immediate reboot. If --force
is specified twice for these operations (with the exception of
kexec), they will be executed immediately, without terminating any
processes or unmounting any file systems. Warning: specifying
--force twice with any of these operations might result in data
loss. Note that when --force is specified twice the selected
operation is executed by systemctl itself, and the system manager
is not contacted. This means the command should succeed even when
the system manager has crashed.

--message=
When used with halt, poweroff or reboot, set a short message
explaining the reason for the operation. The message will be logged
together with the default shutdown message.

--now
When used with enable, the units will also be started. When used
with disable or mask, the units will also be stopped. The start or
stop operation is only carried out when the respective enable or
disable operation has been successful.

--root=
When used with enable/disable/is-enabled (and related commands),
use the specified root path when looking for unit files. If this
option is present, systemctl will operate on the file system
directly, instead of communicating with the systemd daemon to carry
out changes.

--image=image
Takes a path to a disk image file or block device node. If
specified, all operations are applied to file system in the
indicated disk image. This option is similar to --root=, but
operates on file systems stored in disk images or block devices.
The disk image should either contain just a file system or a set of
file systems within a GPT partition table, following the
Discoverable Partitions Specification[1]. For further information
on supported disk images, see systemd-nspawn(1)'s switch of the
same name.

--runtime
When used with enable, disable, edit, (and related commands), make
changes only temporarily, so that they are lost on the next reboot.
This will have the effect that changes are not made in
subdirectories of /etc/ but in /run/, with identical immediate
effects, however, since the latter is lost on reboot, the changes
are lost too.

Similarly, when used with set-property, make changes only
temporarily, so that they are lost on the next reboot.

--preset-mode=
Takes one of "full" (the default), "enable-only", "disable-only".
When used with the preset or preset-all commands, controls whether
units shall be disabled and enabled according to the preset rules,
or only enabled, or only disabled.

-n, --lines=
When used with status, controls the number of journal lines to
show, counting from the most recent ones. Takes a positive integer
argument, or 0 to disable journal output. Defaults to 10.

-o, --output=
When used with status, controls the formatting of the journal
entries that are shown. For the available choices, see
journalctl(1). Defaults to "short".

--firmware-setup
When used with the reboot, poweroff, or halt command, indicate to
the system's firmware to reboot into the firmware setup interface
for the next boot. Note that this functionality is not available on
all systems.

--boot-loader-menu=timeout
When used with the reboot, poweroff, or halt command, indicate to
the system's boot loader to show the boot loader menu on the
following boot. Takes a time value as parameter -- indicating the
menu timeout. Pass zero in order to disable the menu timeout. Note
that not all boot loaders support this functionality.

--boot-loader-entry=ID
When used with the reboot, poweroff, or halt command, indicate to
the system's boot loader to boot into a specific boot loader entry
on the following boot. Takes a boot loader entry identifier as
argument, or "help" in order to list available entries. Note that
not all boot loaders support this functionality.

--reboot-argument=
This switch is used with reboot. The value is architecture and
firmware specific. As an example, "recovery" might be used to
trigger system recovery, and "fota" might be used to trigger a
"firmware over the air" update.

--plain
When used with list-dependencies, list-units or list-machines, the
output is printed as a list instead of a tree, and the bullet
circles are omitted.

--timestamp=
Change the format of printed timestamps. The following values may
be used:

pretty (this is the default)
"Day YYYY-MM-DD HH:MM:SS TZ"

unix
"@seconds-since-the-epoch"

us, <micro>s
"Day YYYY-MM-DD HH:MM:SS.UUUUUU TZ"

utc
"Day YYYY-MM-DD HH:MM:SS UTC"

us+utc, <micro>s+utc
"Day YYYY-MM-DD HH:MM:SS.UUUUUU UTC"

--mkdir
When used with bind, creates the destination file or directory
before applying the bind mount. Note that even though the name of
this option suggests that it is suitable only for directories, this
option also creates the destination file node to mount over if the
object to mount is not a directory, but a regular file, device
node, socket or FIFO.

--marked
Only allowed with reload-or-restart. Enqueues restart jobs for all
units that have the "needs-restart" mark, and reload jobs for units
that have the "needs-reload" mark. When a unit marked for reload
does not support reload, restart will be queued. Those properties
can be set using set-property Markers=....

Unless --no-block is used, systemctl will wait for the queued jobs
to finish.

--read-only
When used with bind, creates a read-only bind mount.

-H, --host=
Execute the operation remotely. Specify a hostname, or a username
and hostname separated by "@", to connect to. The hostname may
optionally be suffixed by a port ssh is listening on, separated by
":", and then a container name, separated by "/", which connects
directly to a specific container on the specified host. This will
use SSH to talk to the remote machine manager instance. Container
names may be enumerated with machinectl -H HOST. Put IPv6 addresses
in brackets.

-M, --machine=
Execute operation on a local container. Specify a container name to
connect to, optionally prefixed by a user name to connect as and a
separating "@" character. If the special string ".host" is used in
place of the container name, a connection to the local system is
made (which is useful to connect to a specific user's user bus:
"--user --machine=lennart@.host"). If the "@" syntax is not used,
the connection is made as root user. If the "@" syntax is used
either the left hand side or the right hand side may be omitted
(but not both) in which case the local user name and ".host" are
implied.

--no-pager
Do not pipe output into a pager.

--legend=BOOL
Enable or disable printing of the legend, i.e. column headers and
the footer with hints. The legend is printed by default, unless
disabled with --quiet or similar.

-h, --help
Print a short help text and exit.

--version
Print a short version string and exit.

EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.

systemctl uses the return codes defined by LSB, as defined in LSB
3.0.0[2].

The mapping of LSB service states to systemd unit states is imperfect,
so it is better to not rely on those return values but to look for
specific unit states and substates instead.

ENVIRONMENT
$SYSTEMD_EDITOR
Editor to use when editing units; overrides $EDITOR and $VISUAL. If
neither $SYSTEMD_EDITOR nor $EDITOR nor $VISUAL are present or if
it is set to an empty string or if their execution failed,
systemctl will try to execute well known editors in this order:
editor(1), nano(1), vim(1), vi(1).

$SYSTEMD_LOG_LEVEL
The maximum log level of emitted messages (messages with a higher
log level, i.e. less important ones, will be suppressed). Either
one of (in order of decreasing importance) emerg, alert, crit, err,
warning, notice, info, debug, or an integer in the range 0...7. See
syslog(3) for more information.

$SYSTEMD_LOG_COLOR
A boolean. If true, messages written to the tty will be colored
according to priority.

This setting is only useful when messages are written directly to
the terminal, because journalctl(1) and other tools that display
logs will color messages based on the log level on their own.

$SYSTEMD_LOG_TIME
A boolean. If true, console log messages will be prefixed with a
timestamp.

This setting is only useful when messages are written directly to
the terminal or a file, because journalctl(1) and other tools that
display logs will attach timestamps based on the entry metadata on
their own.

$SYSTEMD_LOG_LOCATION
A boolean. If true, messages will be prefixed with a filename and
line number in the source code where the message originates.

Note that the log location is often attached as metadata to journal
entries anyway. Including it directly in the message text can
nevertheless be convenient when debugging programs.

$SYSTEMD_LOG_TARGET
The destination for log messages. One of console (log to the
attached tty), console-prefixed (log to the attached tty but with
prefixes encoding the log level and "facility", see syslog(3), kmsg
(log to the kernel circular log buffer), journal (log to the
journal), journal-or-kmsg (log to the journal if available, and to
kmsg otherwise), auto (determine the appropriate log target
automatically, the default), null (disable log output).

$SYSTEMD_PAGER, $PAGER
Pager to use when --no-pager is not given. $SYSTEMD_PAGER is used
if set; otherwise $PAGER is used. If neither $SYSTEMD_PAGER nor
$PAGER are set, a set of well-known pager implementations is tried
in turn, including less(1) and more(1), until one is found. If no
pager implementation is discovered, no pager is invoked. Setting
those environment variables to an empty string or the value "cat"
is equivalent to passing --no-pager.

Note: if $SYSTEMD_PAGERSECURE is not set, $SYSTEMD_PAGER and $PAGER
can only be used to disable the pager (with "cat" or ""), and are
otherwise ignored.

$SYSTEMD_LESS
Override the options passed to less (by default "FRSXMK").

Users might want to change two options in particular:

K
This option instructs the pager to exit immediately when Ctrl+C
is pressed. To allow less to handle Ctrl+C itself to switch
back to the pager command prompt, unset this option.

If the value of $SYSTEMD_LESS does not include "K", and the
pager that is invoked is less, Ctrl+C will be ignored by the
executable, and needs to be handled by the pager.

X
This option instructs the pager to not send termcap
initialization and deinitialization strings to the terminal. It
is set by default to allow command output to remain visible in
the terminal even after the pager exits. Nevertheless, this
prevents some pager functionality from working, in particular
paged output cannot be scrolled with the mouse.

Note that setting the regular $LESS environment variable has no
effect for less invocations by systemd tools.

See less(1) for more discussion.

$SYSTEMD_LESSCHARSET
Override the charset passed to less (by default "utf-8", if the
invoking terminal is determined to be UTF-8 compatible).

Note that setting the regular $LESSCHARSET environment variable has
no effect for less invocations by systemd tools.

$SYSTEMD_PAGERSECURE
Common pager commands like less(1), in addition to "paging", i.e.
scrolling through the output, support opening of or writing to
other files and running arbitrary shell commands. When commands are
invoked with elevated privileges, for example under sudo(8) or
pkexec(1), the pager becomes a security boundary. Care must be
taken that only programs with strictly limited functionality are
used as pagers, and unintended interactive features like opening or
creation of new files or starting of subprocesses are not allowed.
"Secure mode" for the pager may be enabled as described below, if
the pager supports that (most pagers are not written in a way that
takes this into consideration). It is recommended to either
explicitly enable "secure mode" or to completely disable the pager
using --no-pager or PAGER=cat when allowing untrusted users to
execute commands with elevated privileges.

This option takes a boolean argument. When set to true, the "secure
mode" of the pager is enabled. In "secure mode", LESSSECURE=1 will
be set when invoking the pager, which instructs the pager to
disable commands that open or create new files or start new
subprocesses. Currently only less(1) is known to understand this
variable and implement "secure mode".

When set to false, no limitation is placed on the pager. Setting
SYSTEMD_PAGERSECURE=0 or not removing it from the inherited
environment may allow the user to invoke arbitrary commands.

When $SYSTEMD_PAGERSECURE is not set, systemd tools attempt to
automatically figure out if "secure mode" should be enabled and
whether the pager supports it. "Secure mode" is enabled if the
effective UID is not the same as the owner of the login session,
see geteuid(2) and sd_pid_get_owner_uid(3), or when running under
sudo(8) or similar tools ($SUDO_UID is set [3]). In those cases,
SYSTEMD_PAGERSECURE=1 will be set and pagers which are not known to
implement "secure mode" will not be used at all. Note that this
autodetection only covers the most common mechanisms to elevate
privileges and is intended as convenience. It is recommended to
explicitly set $SYSTEMD_PAGERSECURE or disable the pager.

Note that if the $SYSTEMD_PAGER or $PAGER variables are to be
honoured, other than to disable the pager, $SYSTEMD_PAGERSECURE
must be set too.

$SYSTEMD_COLORS
Takes a boolean argument. When true, systemd and related utilities
will use colors in their output, otherwise the output will be
monochrome. Additionally, the variable can take one of the
following special values: "16", "256" to restrict the use of colors
to the base 16 or 256 ANSI colors, respectively. This can be
specified to override the automatic decision based on $TERM and
what the console is connected to.

$SYSTEMD_URLIFY
The value must be a boolean. Controls whether clickable links
should be generated in the output for terminal emulators supporting
this. This can be specified to override the decision that systemd
makes based on $TERM and other conditions.

SEE ALSO
systemd(1), journalctl(1), loginctl(1), machinectl(1), systemd.unit(5),
systemd.resource-control(5), systemd.special(7), wall(1),
systemd.preset(5), systemd.generator(7), glob(7)

NOTES
1. Discoverable Partitions Specification
https://systemd.io/DISCOVERABLE_PARTITIONS

2. LSB 3.0.0
http://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/iniscrptact.html

3. It is recommended for other tools to set and check $SUDO_UID as
appropriate, treating it is a common interface.

systemd 252 SYSTEMCTL(1)

Czas wygenerowania: 0.00037 sek.

Created with the man page lookup class by Andrew Collington.
Based on a C man page viewer by Vadim Pavlov
Unicode soft-hyphen fix (as used by RedHat) by Dan Edwards
Some optimisations by Eli Argon
Caching idea and code contribution by James Richardson

Copyright © 2003-2025 Linux.pl
Hosted by Hosting Linux.pl