DEVEL15-windows-callbacks-20070909

when suspending only clear callbacks for servers that are in an up state.
if they were in a down state, then we couldn't send the clear callbacks
message but more importantly, we need to leave the callback info current
because the callbacks should not be cleared until the server is once again
reachable.

(cherry picked from commit 7a6e406b803115176b9d8d2c235f5c729631103f)

diff --git a/src/WINNT/afsd/cm_scache.c b/src/WINNT/afsd/cm_scache.c
index cf93f282b08dd912b2ab227f44ffc38fcde43871..06e4b2017a03dc1d40dadb5d83e535c021558bb8 100644 (file)
--- a/src/WINNT/afsd/cm_scache.c
+++ b/src/WINNT/afsd/cm_scache.c
@@ -480,7 +480,8 @@ cm_SuspendSCache(void)
     lock_ObtainWrite(&cm_scacheLock);
     for ( scp = cm_data.allSCachesp; scp;
           scp = scp->allNextp ) {
-        if (scp->cbServerp) {
+        if (scp->cbServerp && 
+            !(scp->cbServerp->flags & CM_SERVERFLAG_DOWN)) {
             cm_PutServer(scp->cbServerp);
             scp->cbServerp = NULL;
         }