Re: Antw: Re: crmsh fails to stop already stopped resource

Hi,

On Wed, Feb 18, 2015 at 08:21:10AM +0100, Ulrich Windl wrote:
> >>> Kristoffer Gr=F6nlund<[email protected]> schrieb am 16.02.2015 um 09=
:15 in
> Nachricht <[email protected]>:
> > Vladislav Bogdanov <[email protected]> writes:
> > =

> >> Hi Kristoffer,
> >>
> >> may be it is worth to silently (or at least with rc=3D0) allow deletio=
n of =

> >> non-existing or already-deleted configuration statements?
> >>
> >> Background for that is that I keep track of the all configuration =

> >> statements myself, and, when I delete some resources (together with =

> >> accompanying constraints), they may go "out-of-order" to 'crm configur=
e =

> >> delete', thus some constraints are automatically deleted when deleting =

> >> "lower" resource before the "upper" one. That leads to the whole crm =

> >> script to fail.
> > =

> > Hmm, I am not sure about doing this by default, since we would want to
> > show some kind of indication that a resource name may have been
> > misspelled for example... But I can imagine having a command line flag
> > for being more flexible in this regard.
> =

> I'd agree: Stopping a stopped resource is different from deleting a resou=
rce
> that does not exist (maybe never existed). Maybe (for scripting) crm shell
> would benefit from a "crm resource exists <rsc_name>" returning a status
> (yes/no/error).

You could use crm resource status for that. It should exit with
error only if the resource doesn't exist.

Thanks,

Dejan

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems