Title: Bericht
Servers 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-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 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
 
 

Reply via email to