According to your config, this shouldn't happen. Unchecked evals to OK, in
dependency checking (although I am not an expert in that part of the code).
From mon.8:
Successful opera�
tional statuses (which evaluate to "1") are
"STAT_OK", "STAT_COLDSTART", "STAT_WARMSTART", and
"STAT_UNKNOWN". The word "SELF" (in all caps) can
be used for the group (e.g. "SELF:service"), and is
an abbreviation for the current watch group.
Can you run the server in debug mode, which logs dependency checks, and see
what the output of the dependencies says?
andrew
At 10:01 AM 10/9/01 -0400, Luke Hankins wrote:
>(using mon 99.2)
>
>So if I've got one watch that depends on a few others like so:
>
>watch tree
> service tree
> depend SELF:roots && SELF:leaves
> <etc, etc>
>service roots
> <etc, etc>
>service leaves
> <etc, etc>
>
>
>If, on startup, service 'tree' fires before 'roots' and 'leaves', it'll
>alert.How do I stop this?
>
>
>The docs say: "If dep_behavior is set to 'a', and a parent dependency is
>failing, then suppress the alert."Can this be changed to "...and a
>parent dependency is untested or failing..." somehow?
>
>(I can dodge the issue by setting the 'tree' service to an interval longer
>than the others and turning of randstart, but that's a bummer.)
>
>-Luke
