Hello,
thanks for your fast replies.
matilda matilda wrote:
Peter Kruse <[EMAIL PROTECTED]> 16.07.2007 10:58 >>>
1) MailTo RA does have the monitor call. So it can be called
and the required API is fullfilled.
2) In the case of MailTo the output of 'monitor' is a warning
to the log. You can monitor (requirement) but you need not.
3) 'monitor' doesn't make sense to MailTo as this is a 'oneshot'
RA, because there is no ongoing process after calling start.
Does this help?
This was indeed exactly the answers I was anticipating.
So, if I'm not forced to specify a monitor action in
my cib, then I might also not define a monitor action
for my filesystem resource. Because once it's mounted,
it's mounted, isn't it? And if another resource
like apache is running on top of it, it cannot not
be unmounted anyways. So it really does not make
any sense to check for the filesystem being mounted
every monitor interval.
Makes sense? Even if you don't agree you should accept
that it would be perfectly legal to do this.
My second question is:
If I haven't defined a monitor action in my cib
for a resource, will heartbeat still probe it?
Peter
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
