reload(8) - init daemon control tool
       Connect to init(8) daemon using the D-Bus session bus (for testing purposes only).
       Communication  with  the  init(8)  daemon  is normally performed over a private socket connection.
       This has the advantage of speed and robustness, when issuing commands to start or stop services or
       even reboot the system you do not want to be affected by changes to the D-Bus system bus daemon.

       The  disadvantage  to  using the private socket however is security, init(8) only permits the root
       user to communicate over this socket which means that read-only commands such as status  and  list
       cannot be made by other users.

       The --system option instructs initctl to communicate via the D-Bus system bus rather than over the
       private socket.

       This is only possible if the system bus daemon is running and if init(8) is connected to it.   The
       advantage  is  that  the  default  security  configuration  allows non-root users to use read-only
--dest Specifies the well-known name of the init(8) daemon when using --system.

       There is normally no  need  to  use  this  option  since  the  init(8)  daemon  uses  the  default
       com.ubuntu.Upstart name.  However it may be useful for debugging.
       Applies to the start, stop, restart and emit commands.

       Normally initctl will wait for the command to finish before returning.

       For  the  start,  stop and restart commands, finishing means that the named job is running (or has
       finished for tasks) or has been fully stopped.

       For the emit command, finishing means that all of the jobs affected by the event are  running  (or
       have finished for tasks) or have been fully stopped.

       This option instead causes these commands to only wait for the goal change or event to be queued.
       Reduces output of all commands to errors only.
-i [EVENTS], --ignore-events [EVENTS]

       If specified, the argument should be a  list  of  comma-separated  events  to  ignore  when
       checking the job configuration files.

       This  option may be useful to ignore errors if a particular job configuration file does not
       advertise it emits an event.

       Note that internal events (such as startup(7) and starting(7)) are automatically ignored.
-w, --warn
       If specified, treat any unknown jobs and events as errors.