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,