From 774c5432757676f95d33e7c1e1c05e1f25294eff Mon Sep 17 00:00:00 2001 From: Russ Allbery Date: Thu, 9 Nov 2006 23:58:43 +0000 Subject: [PATCH] DEVEL15-afsd-shutdown-doc-improvement-20061105 Change the CAUTIONS about afsd -shutdown to be less dire and more accurate, as this now mostly works on Linux. (cherry picked from commit f82012552166a51edf6931b05abd0380c429d6b6) --- doc/man-pages/pod8/afsd.pod | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/doc/man-pages/pod8/afsd.pod b/doc/man-pages/pod8/afsd.pod index 428d13f..24c0788 100644 --- a/doc/man-pages/pod8/afsd.pod +++ b/doc/man-pages/pod8/afsd.pod @@ -344,11 +344,16 @@ suites. Provide the command name and all option names in full. =head1 CAUTIONS -Do not use the B<-shutdown> parameter. It does not shutdown the Cache -Manager effectively. Instead, halt Cache Manager activity by using the -standard UNIX B command to unmount the AFS root directory (by -convention, F). The machine must then be rebooted to reinitialize -the Cache Manager. +Before using the B<-shutdown> parameter, use the standard UNIX B +command to unmount the AFS root directory (by convention, F). On +Linux, unloading the AFS kernel module and then loading it again before +restarting AFS after B<-shutdown> is recommended. + +AFS has for years had difficulties with being stopped and restarted +without an intervening reboot. While most of these issues have been +ironed out, stopping and restarting AFS is not recommended unless +necessary and rebooting before restarting AFS is still the safest course +of action. =head1 OPTIONS -- 1.9.4