Title: Bericht
If anything is broken, it's your ISP, not SA. I
think you'd do better trying to
get that fixed, rather than requesting that SK
changes to work around your
problem.
As it is, you could always 'wrapper' an extra ISP
check around each of your
server checks.
P.
networksSent: Wed Aug 20 9:30 AMTo:
[EMAIL PROTECTED]Subject: RE: [SA-list] Suggestion: recheck
dependent tests on second-knock
Okay, but I don't agree with that 100%. If SA
gives just a view of the situation at the time of the check you
won't have to do a second knock at all. If
s 2003 21:26Aan:
[EMAIL PROTECTED]Onderwerp: RE: [SA-list] Suggestion: recheck
dependent tests on second-knock
However you change it you will always have a possibility were you "just
missed" the down of the entry above the entrythat's just the way it
is. The checks are alw
er it.
dirk.
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Robert Haerkens / Native
networksSent: Tue Aug 19 8:38 PMTo:
[EMAIL PROTECTED]Subject: RE: [SA-list] Suggestion: recheck
dependent tests on second-knock
Dirk,
The way SK is
implem
CTED] [mailto:[EMAIL PROTECTED] Namens
Dirk BulinckxVerzonden: dinsdag 19 augustus 2003
18:58Aan: [EMAIL PROTECTED]Onderwerp: RE: [SA-list]
Suggestion: recheck dependent tests on second-knock
Servers Alive will recheck those that depend on the SK item, that's the
right way to d
5:43 PMTo:
[EMAIL PROTECTED]Subject: [SA-list] Suggestion: recheck dependent
tests on second-knock
I have a
suggestion but I don't think it is very easy:
Would it be
possible to change the behaviour of the "second knock" function so it
"re-tests" not
Title: Bericht
I have a
suggestion but I don't think it is very easy:
Would it be
possible to change the behaviour of the "second knock" function so it "re-tests"
not only the failed test but also the test where the failed test depends on?
We use SA to test
over the Internet. Before w
