namespace (i.e. with RootImage=, PrivateMounts=, etc.). Note that the namespace mentioned here where the image mount will be
           added to, is the one where the main service process runs. Note that the namespace mentioned here, where the bind mount will be added to, is the one where the main service process runs. Other processes (those
           exececuted by ExecReload=, ExecStartPre=, etc.) run in distinct namespaces.

           Example:

               systemctl mount-image foo.service /tmp/img.raw /var/lib/image root:ro,nosuid

               systemctl mount-image --mkdir bar.service /tmp/img.raw /var/lib/baz/img

       service-log-level SERVICE [LEVEL]
           If the LEVEL argument is not given, print the current log level as reported by service SERVICE.

           If the optional argument LEVEL is provided, then change the current log level of the service to LEVEL. The log level should be a typical syslog log level, i.e. a value in the range 0...7 or one of the strings
           emerg, alert, crit, err, warning, notice, info, debug; see syslog(3) for details.

           The service must have the appropriate BusName=destination property and also implement the generic org.freedesktop.LogControl1(5) interface. (systemctl will use the generic D-Bus protocol to access the
           org.freedesktop.LogControl1.LogLevel interface for the D-Bus name destination.)

       service-log-target SERVICE [TARGET]
           If the TARGET argument is not given, print the current log target as reported by service SERVICE.

           If the optional argument TARGET is provided, then change the current log target of the service to TARGET. The log target should be one of the strings console (for log output to the service's standard error
           stream), kmsg (for log output to the kernel log buffer), journal (for log output to systemd‐journald.service(8) using the native journal protocol), syslog (for log output to the classic syslog socket /dev/log),
           null (for no log output whatsoever) or auto (for an automatically determined choice, typically equivalent to console if the service is invoked interactively, and journal or syslog otherwise).

           For most services, only a small subset of log targets make sense. In particular, most "normal" services should only implement console, journal, and null. Anything else is only appropriate for low-level services
           that are active in very early boot before proper logging is established.

           The service must have the appropriate BusName=destination property and also implement the generic org.freedesktop.LogControl1(5) interface. (systemctl will use the generic D-Bus protocol to access the
           org.freedesktop.LogControl1.LogLevel interface for the D-Bus name destination.)

       reset-failed [PATTERN...]
           Reset the "failed" state of the specified units, or if no unit name is passed, reset the state of all units. When a unit fails in some way (i.e. process exiting with non-zero error code, terminating abnormally or
           timing out), it will automatically enter the "failed" state and its exit code and status is recorded for introspection by the administrator until the service is stopped/re-started or reset with this command.

           In addition to resetting the "failed" state of a unit it also resets various other per-unit properties: the start rate limit counter of all unit types is reset to zero, as is the restart counter of service units.
           Thus, if a unit's start limit (as configured with StartLimitIntervalSec=/StartLimitBurst=) is hit and the unit refuses to be started again, use this command to make it startable again.

   Unit File Commands
       list-unit-files [PATTERN...]
           List unit files installed on the system, in combination with their enablement state (as reported by is-enabled). If one or more PATTERNs are specified, only unit files whose name matches one of them are shown
           (patterns