Document that the `shutdown` command must be on the $PATH

- Fixes GH-6449
- Closes GH-6450
This commit is contained in:
Seth Vargo 2015-11-26 12:22:23 -05:00
parent 32bb316564
commit 2f2c442457
2 changed files with 11 additions and 2 deletions

View File

@ -12,8 +12,11 @@ destroys all resources that were created during the machine creation process.
After running this command, your computer should be left at a clean state,
as if you never created the guest machine in the first place.
This command usually asks for confirmation before destroying. This
confirmation can be skipped by passing in the `-f` or `--force` flag.
For linux-based guests, Vagrant uses the `shutdown` command to gracefully
terminate the machine. Due to the varying nature of operating systems, the
`shutdown` command may exist at many different locations in the guest's `$PATH`.
It is the guest machine's responsibility to properly populate the `$PATH` with
directory containing the `shutdown` command.
## Options

View File

@ -13,6 +13,12 @@ Vagrant will first attempt to gracefully shut down the machine by running
the guest OS shutdown mechanism. If this fails, or if the `--force` flag is
specified, Vagrant will effectively just shut off power to the machine.
For linux-based guests, Vagrant uses the `shutdown` command to gracefully
terminate the machine. Due to the varying nature of operating systems, the
`shutdown` command may exist at many different locations in the guest's `$PATH`.
It is the guest machine's responsibility to properly populate the `$PATH` with
directory containing the `shutdown` command.
## Options
* `-f` or `--force` - Don't attempt to gracefully shut down the machine.