Translations by Scott James Remnant (Canonical)

Restart job.

JOB is the name of the job that is to be restarted, this may be followed by zero or more environment variables to be defined in the job after restarting. The environment also serves to distinguish between job instances, and thus decide which of multiple instances will be restarted.

Send HUP signal to job.

JOB is the name of the job that is to be sent the signal, this may be followed by zero or more environment variables to distinguish between job instances.

Query status of job.

JOB is the name of the job that is to be queried, this may be followed by zero or more environment variables to distguish between job instances.

List known jobs.

The known jobs and their current status will be output.

EVENT [KEY=VALUE]...

Emit an event.

EVENT is the name of an event the init daemon should emit, this may be followed by zero or more environment variables to be included in the event.

Reload the configuration of the init daemon.

Request the version of the init daemon.

[PRIORITY]

Change the minimum priority of log messages from the init daemon

PRIORITY may be one of: `debug' (messages useful for debugging upstart are logged, equivalent to --debug on kernel command-line); `info' (messages about job goal and state changes, as well as event emissions are logged, equivalent to --verbose on the kernel command-line); `message' (informational and debugging messages are suppressed, the default); `warn' (ordinary messages are suppressed whilst still logging warnings and errors); `error' (only errors are logged, equivalent to --quiet on the kernel command-line) or `fatal' (only fatal errors are logged). Without arguments, this outputs the current log priority.

don't sync before reboot or halt

force reboot or halt, don't call shutdown(8)

switch off the power when called as halt

don't actually reboot or halt, just write wtmp record

Halt the system.

Power off the system.

Reboot the system.

This command is intended to instruct the kernel to reboot or halt the system; when run without the -f option, or when in a system runlevel other than 0 or 6, it will actually execute /sbin/shutdown.

Calling shutdown

Unable to execute shutdown: %s

Rebooting

Halting

Powering off

[UTMP]

Output previous and current runlevel.

The system /var/run/utmp file is used unless the alternate file UTMP is given.

reboot after shutdown

halt or power off after shutdown

halt after shutdown (implies -h)

power off after shutdown (implies -h)

cancel a running shutdown

only send warnings, don't shutdown

TIME [MESSAGE]

Bring the system down.

TIME may have different formats, the most common is simply the word 'now' which will bring the system down immediately. Other valid formats are +m, where m is the number of minutes to wait until shutting down and hh:mm which specifies the time on the 24hr clock. Logged in users are warned by a message sent to their terminal, you may include an optional MESSAGE included with this. Messages can be sent without actually bringing the system down by using the -k option. If TIME is given, the command will remain in the foreground until the shutdown occurs. It can be cancelled by Control-C, or by another user using the -c option. The system is brought down into maintenance (single-user) mode by default, you can change this with either the -r or -h option which specify a reboot or system halt respectively. The -h option can be further modified with -H or -P to specify whether to halt the system, or to power it off afterwards. The default is left up to the shutdown scripts.

%s: time expected

%s: illegal hour value

%s: illegal minute value

%s: illegal time value

Shutdown is not running

Another shutdown is already running

Cannot find pid of running shutdown

Unable to change directory

Unable to write pid file