Dirk,
The way SK is
implemented now works fine when servers went down before the test-cycle
starts. It is very likely that a sub-test fails because the test where
it depends on went suddenly down. So, you will get a lot better diagnostic when
SA does one step back in case of a "possible down". It can discover if the
problem is larger.
With SA it's
almost possible to identify the problem exactly when you do the right tests and
make them in the correct order depending on each-other. To test a mailserver I
would first telnet it's Internet router, then try to connect to the SMTP port
and then try to use SMPT2POP3. If one of these tests fails it would be very
usefull if SA could do a step back in dependencies to check out the exact
problem.
Thanks for your
time,
Robert
-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Dirk Bulinckx
Verzonden: dinsdag 19 augustus 2003 18:58
Aan: [EMAIL PROTECTED]
Onderwerp: RE: [SA-list] Suggestion: recheck dependent tests on second-knockServers Alive will recheck those that depend on the SK item, that's the right way to do this, not the other way around.
dirk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Robert Haerkens / Native networks
Sent: Tue Aug 19 5:43 PM
To: [EMAIL PROTECTED]
Subject: [SA-list] Suggestion: recheck dependent tests on second-knockI 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 we do tests we first check if our Internet connection is functioning (if that is not working, you dont have to do other tests since all other tests depend on our Internet connection. This works perfect in theory but in practise when our connections drops (since I use SA I know it drops far more often then the ISP tells me), it always drops in the middle of a test an not exactly before we do our "self-test".Maybe the easiest way is to change the Second Knock to retest the goup in the second knock in stead of the failed test?Robert
