-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.0 - Feature Reqest: '--skip-if-halted' for 'qvm-shutdown' #3032
Comments
Why do we have |
On 2017-08-16 22:31, Bahtiar Gadimov wrote:
Why do we have --skip-if-running at all? I would expect both just to exit with 0 if the VM is already started or shutdown.
Sadly `qvm-start` throws an error insted if the requested vm is running
... as does `qvm-shutdown` if the requested vm is already halted.
|
I agree with @kalkin above, that not having any skipping option at all and just exiting if a vm already exists would be the preferable option for both |
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
Or update dom0 via Qubes Manager. |
Qubes OS version (e.g.,
R3.2
):4.0-rc1
Affected TemplateVMs (e.g.,
fedora-23
, if applicable):dom0
Expected behavior:
Analogous to the capabilities of 'qvm-start' ('--skip-if-running'), 'qvm-shutdown' is expected to have the option '--skip-if-halted'.
Actual behavior:
Not implemented.
The text was updated successfully, but these errors were encountered: