corosync-objctl(8) [suse man page]

COROSYNC-OBJCTL(8)					      System Manager's Manual						COROSYNC-OBJCTL(8)

NAME

       corosync-objctl - Configure objects in the Object Database

SYNOPSIS

       corosync-objctl [-c|-w|-d|-a|-t-h] <OBJECT-SPEC>...

DESCRIPTION

       corosync-objctl is used to configure objects within the object database at runtime.

OBJECT-SPEC
       There are two types of entities
	      Objects and Key=Value pairs

       Objects
	      Objects  are  container  like entities that can hold other entities.  They are specified as "objectA"."objectB".	An example is log-
	      ging.logger.

       Key=Value pairs
	      These are the entities that actually hold values	(read  database  "fields").   They  are  specified  as	object.key=value  or  just
	      object.key if you are reading.

OPTIONS

       -c     Create a new object.

       -d     Delete an existing object.

       -w     Use this option when you want to write a new value to a key.

       -a     Display all values currently available.

       -t     Track  changes  to an object and it's children. As changes are made to the object they are printed out. this is kind of like a "tail
	      -f" for the object database.

       -h     Print basic usage.

EXAMPLES

       Print the objOne object (shouldn't exist yet).
	      $ corosync-objctl objOne

       Create the objOne object.
	      $ corosync-objctl -c objOne

       Print the objOne object (empty).
	      $ corosync-objctl objOne
	      objOne

       Write two new keys to the objOne object.
	      $ corosync-objctl -w objOne.max=3000 objOne.min=100

       Print the objOne object (with the two new keys).
	      $ corosync-objctl objOne
	      objOne.min=100
	      objOne.max=3000

       Delete the objOne.min key
	      $ corosync-objctl -d objOne.min=100

       Prove that is gone.
	      $ corosync-objctl objOne
	      objOne.max=3000

       Delete the whole objOne object.
	      $ corosync-objctl -d objOne

       Prove that is gone.
	      $ corosync-objctl objOne

SEE ALSO

       confdb_initialize(3),

AUTHOR

       Angus Salkeld

								    2008-07-29							COROSYNC-OBJCTL(8)

COROSYNC-NOTIFYD(8)					      System Manager's Manual					       COROSYNC-NOTIFYD(8)

NAME

       corosync-notifyd - Listen for important corosync events and send dbus and/or snmp traps.

SYNOPSIS

       corosync-notifyd [-f] [-l] [-o] [-s] [-m] [manager] [-d] [-h]

DESCRIPTION

       corosync-notifyd uses corosync API to listen for important cluster events and can log them, generate dbus signals or genterate snmp traps.

OPTIONS

       -f     Start application in foreground.

       -l     Log all events.

       -o     Print events to stdout (turns on -l).

       -s     Send SNMP traps on all events.

       -m     Set the SNMP manager address.

       -d     Send DBUS signals on all events.

       -h     Print this help

EXAMPLES

       $ corosync-notifyd -o
       corosync-notifyd[18505]: troll[23374016] corosync-notify:18505:12 is now connected to corosync
       corosync-notifyd[18505]: troll[23374016] corosync-notify:18505:13 is now disconnected from corosync
       corosync-notifyd[18505]: troll[23374016] is now quorate
       corosync-notifyd[18505]: r2[1550100672] ip:192.168.100.92 joined
       corosync-notifyd[18505]: r2[1550100672] ip:192.168.100.92 left

       $ corosync-notifyd -o

       Note this output below is from "dbus-monitor --system"

       signal sender=:1.216 -> dest=(null destination) serial=2 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=ConnectionStateChange
	  string "troll"
	  uint32 23374016
	  string "corosync-notify:18900:12"
	  string "connected"
       signal sender=:1.216 -> dest=(null destination) serial=3 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=ConnectionStateChange
	  string "troll"
	  uint32 23374016
	  string "corosync-notify:18900:13"
	  string "disconnected"
       signal sender=:1.216 -> dest=(null destination) serial=4 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=QorumStateChange
	  string "troll"
	  uint32 23374016
	  string "quorate"
       signal sender=:1.216 -> dest=(null destination) serial=5 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=NodeStateChange
	  string "r2"
	  uint32 1550100672
	  string "192.168.100.92"
	  string "joined"
       signal sender=:1.216 -> dest=(null destination) serial=6 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=NodeStateChange
	  string "r2"
	  uint32 1550100672
	  string "192.168.100.92"
	  string "left"

SEE ALSO

       corosync(8), corosync-objctl(8), dbus-monitor(1),

AUTHOR

       Angus Salkeld

								    2011-01-14						       COROSYNC-NOTIFYD(8)