will be started.

       try-reload-or-restart PATTERN...
           Reload one or more units if they support it. If not, stop and then start them instead. This does nothing if the units are not running.

       isolate UNIT
           Start the unit specified on the command line and its dependencies and stop all others, unless they have IgnoreOnIsolate=yes (see systemd.unit(5)). If a unit name with no extension is given, an extension of
           ".target" will be assumed.

           This command is dangerous, since it will immediately stop processes that are not enabled in the new target, possibly including the graphical environment or terminal you are currently using.

           Note that this operation is allowed only on units where AllowIsolate= is enabled. See systemd.unit(5) for details.

       kill PATTERN...
           Send a signal to one or more processes of the unit. Use --kill-whom= to select which process to kill. Use --signal= to select the signal to send.

       clean PATTERN...
           Remove the configuration, state, cache, logs or runtime data of the specified units. Use --what= to select which kind of resource to remove. For service units this may be used to remove the directories configured
           with ConfigurationDirectory=, StateDirectory=, CacheDirectory=, LogsDirectory= and RuntimeDirectory=, see systemd.exec(5) for details. For timer units this may be used to clear out the persistent timestamp data if
           Persistent= is used and --what=state is selected, see systemd.timer(5). This command only applies to units that use either of these settings. If --what= is not specified, both the cache and runtime data are
           removed (as these two types of data are generally redundant and reproducible on the next invocation of the unit).

       freeze PATTERN...
           Freeze one or more units specified on the command line using cgroup freezer

           Freezing the unit will cause all processes contained within the cgroup corresponding to the unit to be suspended. Being suspended means that unit's processes won't be scheduled to run on CPU until thawed. Note
           that this command is supported only on systems that use unified cgroup hierarchy. Unit is automatically thawed just before we execute a job against the unit, e.g. before the unit is stopped.

       thaw PATTERN...
           Thaw (unfreeze) one or more units specified on the command line.

           This is the inverse operation to the freeze command and resumes the execution of processes in the unit's cgroup.

       set-property UNIT PROPERTY=VALUE...
           Set the specified unit properties at runtime where this is supported. This allows changing configuration parameter properties such as resource control settings at runtime. Not all properties may be changed at
           runtime, but many resource control settings (primarily those in systemd.resource‐control(5)) may. The changes are applied immediately, and stored on disk for future boots, unless --runtime is passed, in which case
           the settings only apply until the next reboot. The syntax of the property assignment follows closely the syntax of assignments in unit files.

           Example: systemctl set-property foobar.service CPUWeight=200

           If the specified unit appears to be inactive, the changes will be only stored on disk as described previously hence they will be effective when the unit will be started.

           Note that this command allows changing multiple properties at the same time, which is preferable over setting them individually.

           Example: systemctl set-property foobar.service CPUWeight=200 MemoryMax=2G IPAccounting=yes

           Like with unit file configuration settings, assigning an empty setting usually resets a property to its defaults.

           Example: systemctl set-property avahi-daemon.service IPAddressDeny=

       bind UNIT PATH [PATH]
           Bind-mounts a file or directory from the host