(see systemd.generator(7)), reload all unit files, and recreate the entire dependency tree. While the daemon is being reloaded, all sockets
           systemd listens on behalf of user configuration will stay accessible.

           This command should not be confused with the reload command.

       daemon-reexec
           Reexecute the systemd manager. This will serialize the manager state, reexecute the process and deserialize the state again. This command is of little use except for debugging and package upgrades. Sometimes, it
           might be helpful as a heavy-weight daemon-reload. While the daemon is being reexecuted, all sockets systemd listening on behalf of user configuration will stay accessible.

       log-level [LEVEL]
           If no argument is given, print the current log level of the manager. If an optional argument LEVEL is provided, then the command changes the current log level of the manager to LEVEL (accepts the same values as
           --log-level= described in systemd(1)).

       log-target [TARGET]
           If no argument is given, print the current log target of the manager. If an optional argument TARGET is provided, then the command changes the current log target of the manager to TARGET (accepts the same values
           as --log-target=, described in systemd(1)).

       service-watchdogs [yes|no]
           If no argument is given, print the current state of service runtime watchdogs of the manager. If an optional boolean argument is provided, then globally enables or disables the service runtime watchdogs
           (WatchdogSec=) and emergency actions (e.g.  OnFailure= or StartLimitAction=); see systemd.service(5). The hardware watchdog is not affected by this setting.

   System Commands
       is-system-running
           Checks whether the system is operational. This returns success (exit code 0) when the system is fully up and running, specifically not in startup, shutdown or maintenance mode, and with no failed services. Failure
           is returned otherwise (exit code non-zero). In addition, the current state is printed in a short string to standard output, see the table below. Use --quiet to suppress this output.

           Use --wait to wait until the boot process is completed before printing the current state and returning the appropriate error status. If --wait is in use, states initializing or starting will not be reported,
           instead the command will block until a later state (such as running or degraded) is reached.

           Table 2. is-system-running output
           ┌──────────────┬─────────────────────────────────────────────────────────┬───────────┐
           │ Name         │ Description                                             │ Exit Code │
           ├──────────────┼─────────────────────────────────────────────────────────┼───────────┤
           │ initializing │ Early bootup, before basic.target is reached or the     │ > 0       │
           │              │ maintenance state entered.                              │           │
           ├──────────────┼─────────────────────────────────────────────────────────┼───────────┤
           │ starting     │ Late bootup, before the job queue becomes idle for the  │ > 0       │
           │              │ first time, or one of the rescue targets are reached.   │           │
           ├──────────────┼─────────────────────────────────────────────────────────┼───────────┤
           │ running      │ The system is fully operational.                        │ 0         │
           ├──────────────┼─────────────────────────────────────────────────────────┼───────────┤
           │ degraded     │ The system is operational but one or more units failed. │ > 0       │
           ├──────────────┼─────────────────────────────────────────────────────────┼───────────┤
           │ maintenance  │ The rescue or emergency target is active.               │ > 0       │
           ├──────────────┼───────────────────────────────────────────────────