On 2006-06-15T03:20:24, linux-ha-cvs@lists.linux-ha.org wrote:
linux-ha CVS committal
Author : sunjd
Host:
Project : linux-ha
Module : lib
Dir : linux-ha/lib/fencing
Modified Files:
stonithd_lib.c
Log Message:
tweaking logs; add more check for ipc functions
On 2006-06-16T12:43:12, Huang Zhen [EMAIL PROTECTED] wrote:
Clone or m/s is NOT a flag you can switch off and on on a primitive. It
is a container for one.
Do you mean adding a clone or m/s first, then add resource to it later?
If no body opposes it, I will do it.
The workload should be less
Various linux-ha-dev emails in the last few days suggest that 2.0.6
might be in preparation. This in turn suggests that we might be in a
code-freeze.
Note the compounded might be uncertainties which I'm having to surmise.
I recall that in years gone by code-freezes were announced to us here on
David Lee wrote:
Various linux-ha-dev emails in the last few days suggest that 2.0.6
might be in preparation. This in turn suggests that we might be in a
code-freeze.
Note the compounded might be uncertainties which I'm having to surmise.
I recall that in years gone by code-freezes were
Dejan Muhamedagic wrote:
Hi,
Forgive my ignorance, but I'd really appreciate if somebody could
explain the following excerpt from Filesystem:
# By sending both signals twice, we eliminate the need
# for `sleep` after them.
for sig in SIGTERM SIGTERM SIGKILL
