libxl: remove force parameter from libxl_domain_destroy

Since a destroy is considered a forced shutdown, there's no point in
passing a force parameter. All the occurences of this function have
been replaced with the proper syntax.

Signed-off-by: Roger Pau Monne <roger.pau@entel.upc.edu>
Acked-by: Ian Jackson <ian.jackson.citrix.com>
Committed-by: Ian Jackson <ian.jackson.citrix.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
This commit is contained in:
Roger Pau Monne committed 2011-12-15 18:55:46 +01:00
1 parent 8e4cd77b8a
commit 0b5c5ae1bd
6 files changed
+14 -14

No files matched your search

+3 -3
View File
@@ -437,10 +437,10 @@ static PyObject *pyxl_domain_shutdown(XlObject *self, PyObject *args)
static PyObject *pyxl_domain_destroy(XlObject *self, PyObject *args)
{
int domid, force = 1;
if ( !PyArg_ParseTuple(args, "i|i", &domid, &force) )
int domid;
if ( !PyArg_ParseTuple(args, "i", &domid) )
return NULL;
if ( libxl_domain_destroy(self->ctx, domid, force) ) {
if ( libxl_domain_destroy(self->ctx, domid) ) {
PyErr_SetString(xl_error_obj, "cannot destroy domain");
return NULL;
}
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.