[Openais] corosync - handle reload configuration and statics update

Patch fixes following situation: 1. objdb receives reload notification and ends in function object_reload_config. This will call objdb_wrlock. I will call this thread #1 2. Another thread will decide to update corosync statistics and calls object_key_increment. This calls objdb_rdlock. This

[Openais] coroipcc.c sem_init/sem_destroy?

Should the coroipcc client library have matching sem_destroy in the hdb_destructor for the corresponding sem_init calls in coroipcc_service_ connect? thanks, dan $ diff -c coroipcc.c coroipcc.c.orig *** coroipcc.c 2010-06-25 16:54:43.0 -0700 --- coroipcc.c-1.2.5 2010-06-25

Re: [Openais] coroipcc.c sem_init/sem_destroy?

On 06/25/2010 05:20 PM, dan clark wrote: Should the coroipcc client library have matching sem_destroy in the hdb_destructor for the corresponding sem_init calls in coroipcc_service_ connect? thanks, dan Dan exec/coroipcs.c executes a sem_destroy on the posix semaphores when the client

[Openais] recover from corosync daemon restart and cpg_finalize timing

Dear Gentle Reader Attached is a small test program to stress initializing and finalizing communication between a corosync cpg client and the corosync daemon. The test was run under version 1.2.4. Initial testing was with a single node, subsequent testing occurred on a system consisting of 3