On Jan 27, 2006, at 3:23 PM, Alan Robertson wrote:
Andrew Beekhof wrote:
On 1/26/06, Alan Robertson [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
On 1/26/06, Alan Robertson [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
CTS testers please note this commit.
In order to run the same tests
Andrew Beekhof wrote:
On Jan 27, 2006, at 3:23 PM, Alan Robertson wrote:
Andrew Beekhof wrote:
On 1/26/06, Alan Robertson [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
On 1/26/06, Alan Robertson [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
CTS testers please note this commit.
In
Andrew Beekhof wrote:
CTS testers please note this commit.
In order to run the same tests as you used to, you need to specify:
enable_config_writes off
in ha.cf
Why is this an ha.cf option. It's clearly a CIB option - so I would
think it belongs in the CIB. It makes no sense there... We
On 1/26/06, Alan Robertson [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
CTS testers please note this commit.
In order to run the same tests as you used to, you need to specify:
enable_config_writes off
in ha.cf
Why is this an ha.cf option. It's clearly a CIB option - so I would
Andrew Beekhof wrote:
On 1/26/06, Alan Robertson [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
CTS testers please note this commit.
In order to run the same tests as you used to, you need to specify:
enable_config_writes off
in ha.cf
Why is this an ha.cf option. It's clearly a CIB option
On 2006-01-26T12:06:33, Alan Robertson [EMAIL PROTECTED] wrote:
Four reasons:
- the CIB is intended to be policy free (and at the moment is IIRC)
BUT this is a CIB policy - hence it must be enforced and carried out by
the CIB.
- correct interpretation of options in the CIB requires
On 1/26/06, Alan Robertson [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
On 1/26/06, Alan Robertson [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
CTS testers please note this commit.
In order to run the same tests as you used to, you need to specify:
enable_config_writes off
in
