On Apr 24, 2006, at 4:53 PM, Alan Robertson wrote:
Lars Marowsky-Bree wrote:
On 2006-04-24T09:50:52, Andrew Beekhof <[EMAIL PROTECTED]> wrote:
Sure. The best reason is that if the user has asked for
multiple concurrent monitor operations, we need to know that all
of them are running.
Previously the LRM would have reported only the last one that ran
and it would have looked to us that the others were not running
and we would "start" them again.
Ah.
Uhm. What could cause concurrent monitor operations - except for
different monitoring depths, I guess? (Just making sure I
understand.)
A question:
Can we restrict heavy-duty monitoring operations to only occur on
weekends, or at night or something like that?
probably not but it would be easy enough to add.
we can already disable an recurring operation with: <op id=...
disable=true/>
that plus cron would probably do for now
I can see wanting to do a heavy-duty monitor (like an fsck) not
only rarely, but also only at certain times...
--
Alan Robertson <[EMAIL PROTECTED]>
"Openness is the foundation and preservative of friendship... Let
me claim from you at all times your undisguised opinions." -
William Wilberforce
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
--
Andrew Beekhof
"I like your old stuff better than your new stuff" - Regurgitator
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
