From: Tom Keiser <tkeiser@gmail.com>
Date: Fri, 5 Oct 2007 04:31:51 +0000 (+0000)
Subject: DEVEL15-dafs-listen-after-restoring-state-20071004
X-Git-Tag: openafs-devel-1_5_26~49
X-Git-Url: https://git.michaelhowe.org/gitweb/?a=commitdiff_plain;h=97628d4e32a6332d3a6239c6412c33c47e1fce5d;p=packages%2Fo%2Fopenafs.git

DEVEL15-dafs-listen-after-restoring-state-20071004


don't start rx server until the previous state has been loaded


(cherry picked from commit f6e59be4dc203f4662d723ab42ed7f07c3367678)
---

diff --git a/src/viced/viced.c b/src/viced/viced.c
index 45357e3b3..6526a377b 100644
--- a/src/viced/viced.c
+++ b/src/viced/viced.c
@@ -2141,7 +2141,18 @@ main(int argc, char *argv[])
     /* allow super users to manage RX statistics */
     rx_SetRxStatUserOk(fs_rxstat_userok);
 
+#if !defined(AFS_DEMAND_ATTACH_FS)
+    /* 
+     * For DAFS, we do not start the Rx server threads until after
+     * the volume package is initialized, and fileserver state is
+     * restored.  This is necessary in order to keep host and callback
+     * package state pristine until we have a chance to restore state.
+     *
+     * Furthermore, startup latency is much lower with dafs, so this
+     * shouldn't pose a serious problem.
+     */
     rx_StartServer(0);		/* now start handling requests */
+#endif
 
     /* we ensure that there is enough space in the vnode buffer to satisfy
      ** requests from all concurrent threads. 
@@ -2181,6 +2192,7 @@ main(int argc, char *argv[])
 	 * restore fileserver state */
 	fs_stateRestore();
     }
+    rx_StartServer(0);  /* now start handling requests */
 #endif /* AFS_DEMAND_ATTACH_FS */
 
     /*