I have heartbeat 2.1.4 running in my Suse server ( x86_64 ).
I have 2 nodes , active-active.
Lets call node A and node B
When we have the resources in A and we start node B , the resources stays in A .
When we have the resources in B and we start node A , the resources move all to node A.
I don't want this. I just want that the resources move to the other node when there is a failover.
I know that it is possible to login into the HMC console and view all the specs like, how much CPU/RAM every LPAR has.
But how can I check how much the whole P7 has in total and how much is left to creat a new LPAR:wall: (5 Replies)
Here is a list of resources for Unix and GNU/Linux bootloaders:
GRUB Legacy: The original GRand Unified Bootloader. Now known as GRUB Legacy.
GRUB: The latest and greatest. More commonly known as GRUB2.
BRUG: Brand-new Universal loadeR from GRUB. Based on GRUB. Adds features like new object... (0 Replies)
I was wondering what is the function in C to free a resource(usually a variable)
I know in C# there a Garbage collector, but in c and C++ there are none.
I believe in c++ the function is free(); (8 Replies)
For some reason, I'm having a bit of a brain fart here and cannot think of a simple solution to this problem...
We have a samba server installed on one of our Darwin boxes. Someone is doing massive amounts of work through a samba share, and in turn in pegging samba and the box. I can see how... (1 Reply)
Good morning all!
Does any know of any good resources to read up on why people would use Unix, what the weaknesses are of the platform and how it is used!
Many thanks:
Note: This is for an assignment, I know you are not suppose to ask for help or post assignment questions but all I am... (2 Replies)
Hi all
I would like to check my production machine and find out which application is using up the resources of the Unix machine, is there a way to display individual applications that are running and the percentage of resources they are taking up? (2 Replies)
CRM_STANDBY(8) [FIXME: manual] CRM_STANDBY(8)NAME
crm_standby - manipulate a node's standby attribute to determine whether resources can be run on this node
SYNOPSIS
crm_standby [-?|-V] -D -u|-U node -r resource
crm_standby [-?|-V] -G -u|-U node -r resource
crm_standby [-?|-V] -v string -u|-U node -r resource [-l string]
DESCRIPTION
The crm_standby command manipulates a node's standby attribute. Any node in standby mode is no longer eligible to host resources and any
resources that are there must be moved. Standby mode can be useful for performing maintenance tasks, such as kernel updates. Remove the
standby attribute from the node when it should become a fully active member of the cluster again.
By assigning a lifetime to the standby attribute, determine whether the standby setting should survive a reboot of the node (set lifetime
to forever) or should be reset with reboot (set lifetime to reboot). Alternatively, remove the standby attribute and bring the node back
from standby manually.
OPTIONS --help, -?
Print a help message.
--verbose, -V
Turn on debug information.
Note
Increase the level of verbosity by providing additional instances.
--quiet, -Q
When doing an attribute query using -G, print just the value to stdout. Use this option with -G.
--get-value, -G
Retrieve rather than set the preference.
--delete-attr, -D
Specify the attribute to delete.
--attr-value string, -v string
Specify the value to use. This option is ignored when used with -G.
--node-uuid node_uuid, -u node_uuid
Specify the UUID of the node to change.
--node-uname node_uname, -U node_uname
Specify the uname of the node to change.
--lifetime string, -l string
Determine how long this preference lasts. Possible values are reboot or forever.
Note
If a forever value exists, it is always used by the CRM instead of any reboot value.
EXAMPLES
Have a local node go to standby:
crm_standby -v true
Have a node (node1) go to standby:
crm_standby -v true -U node1
Query the standby status of a node:
crm_standby -G -U node1
Remove the standby property from a node:
crm_standby -D -U node1
Have a node go to standby for an indefinite period of time:
crm_standby -v true -l forever -U node1
Have a node go to standby until the next reboot of this node:
crm_standby -v true -l reboot -U node1
FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.
SEE ALSO
???, ???
AUTHOR
crm_standby was written by Andrew Beekhof.
[FIXME: source] 07/05/2010 CRM_STANDBY(8)