On Mar 14, 2008, at 4:34 PM, Michael Schwartzkopff wrote:
Am Freitag, 14. März 2008 16:25 schrieb Andreas Mock:
Hi,
the behaviour also on depends on stop_orphan_resources of the
crm_config.
Hi Michael,
thank you for your reply. I assumed this. That's why I wrote
that my setting of 'stop-orphan-resources=true'.
Do you know how it behaves in this situation?
this option will stop orphan resources. If there is no definition in
the CIB
any more. In the definition your could tell not to care about this
resource
(is_managed=false).
If you do not want to stop that resource after removal, I would
suggest to
set stop_orphan_resources=false
nod
set is_managed to false=false
The global is_managed_default option is probably a better setting to
change in this case.
remove the resource
clean up the orphan.
set stop_orphan_resources=true
And set is_managed_default back to true again
But this is only my suggestion. Please test this with a test
cluster. XEN is
your friend!
Greetings,
--
Dr. Michael Schwartzkopff
MultiNET Services GmbH
Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany
Tel: +49 - 89 - 45 69 11 0
Fax: +49 - 89 - 45 69 11 21
mob: +49 - 174 - 343 28 75
mail: [EMAIL PROTECTED]
web: www.multinet.de
Sitz der Gesellschaft: 85630 Grasbrunn
Registergericht: Amtsgericht München HRB 114375
Geschäftsführer: Günter Jurgeneit, Hubert Martens
---
PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B
Skype: misch42
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
