* Change the documentation of afsd -shutdown to be less dire and more

  accurate.  Thanks, Daniel J. Priem.  (Closes: #394990)

diff --git a/debian/changelog b/debian/changelog
index fcf6770c435bf5dd1a4b3c7470ba22040dc6e224..1ec83b53d334ae58165f2e489504f2caa4540ea4 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+openafs (1.4.2-3) unstable; urgency=low
+
+  * Change the documentation of afsd -shutdown to be less dire and more
+    accurate.  Thanks, Daniel J. Priem.  (Closes: #394990)
+
+ -- Russ Allbery <rra@debian.org>  Sun,  5 Nov 2006 20:11:36 -0800
+
 openafs (1.4.2-2) unstable; urgency=low
 
   * Upstream fix to prevent butc segfaulting.

diff --git a/doc/man-pages/pod8/afsd.pod b/doc/man-pages/pod8/afsd.pod
index 428d13f5b09bc6e8d485939aefc2da1861d6757e..24c07889f774314e431cd8964d8b8f54442c705e 100644 (file)
--- 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<umount> command to unmount the AFS root directory (by
-convention, F</afs>). The machine must then be rebooted to reinitialize
-the Cache Manager.
+Before using the B<-shutdown> parameter, use the standard UNIX B<umount>
+command to unmount the AFS root directory (by convention, F</afs>).  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