Re: [Linux-ha-dev] What happened to rsc_state?

2006-05-10 Thread Andrew Beekhof
On 5/9/06, Peter Kruse [EMAIL PROTECTED] wrote: Hi, Andrew Beekhof wrote: if you want a list of failed resources: crm_mon -1 | grep failed if you just want the lrm_rsc_op's that failed, look for rc_code != 0 rc_code != 7 (where 7 is LSB for Safely Stopped) in the result of cibadmin -Ql

Re: [Linux-ha-dev] What happened to rsc_state?

2006-05-10 Thread Peter Kruse
Hi, Andrew Beekhof wrote: On 5/9/06, Peter Kruse [EMAIL PROTECTED] wrote: although cibadmin -Ql -o status does not show the failed resource anymore. How can I recover from this situation? cib contents? Oh, thanks for reminding me (I should know by now...) attached is output of cibadmin

[Linux-ha-dev] Autoconf Macro for swig (AC_PATH_PROGS)

2006-05-10 Thread Brian A. Seklecki
When this macro fails, it sets: config.log:SWIG='swig not found' config.status:s,@SWIG@,swig not found,;t t ...instead of causing a configure failure. This pasive failure later translates into attemps to exec the program swig with argument not present. We might add a hook to check if

[Linux-ha-dev] send_arp.c -Werror in heartbeat/libnet_util

2006-05-10 Thread Brian A. Seklecki
When compiling send_arp.c the compiler warns about some functions and then bombs out due to -Werror: In file included from /usr/local/include/libnet.h:124, from send_arp.c:37: /usr/local/include/./libnet/libnet-functions.h:1840: warning: function declaration isn't a

[Linux-ha-dev] Re: send_arp.c -Werror in heartbeat/libnet_util

2006-05-10 Thread Brian A. Seklecki
Apparently GCC 3.4.4 wants the prototypes to have a (void) in the prototype argument list (Thank you Bill Moran). Honestly, I can't even see where these these actual functions are (recursive grep), so it must be a prototype/macro, or prototypes for non-existant functions. I imagine that's

Re: [Linux-ha-dev] Autoconf Macro for swig (AC_PATH_PROGS)

2006-05-10 Thread Alan Robertson
Brian A. Seklecki wrote: When this macro fails, it sets: config.log:SWIG='swig not found' config.status:s,@SWIG@,swig not found,;t t ...instead of causing a configure failure. This pasive failure later translates into attemps to exec the program swig with argument not present. We might