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-warn
           Don't generate the warnings shown by default in the following cases:

           •   when systemctl is invoked without procfs mounted on /proc/,

           •   when using enable or disable on units without install information (i.e. don't have or have an empty [Install] section).

       --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