Require $remote_fs before stopping as well

This isn't strictly necessary, but it avoids the Lintian warning and we
can clean it up after finding a better approach for what /usr/bin/fs
currently does.

diff --git a/debian/changelog b/debian/changelog
index 12d533408e1fe77f160fa06fe95ebfbadb5e09d6..fab38ed188223951eabe932e0cb5c5602830d276 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -16,9 +16,9 @@ openafs (1.4.12~pre4+dfsg-1) UNRELEASED; urgency=low
   * Use dh_dkms from the DKMS package to handle creation of the maintainer
     scripts for openafs-modules-dkms rather than rolling our own.
     (LP: #497149)
-  * Update init script to require $remote_fs be started first.  This won't
-    be the case in the long run, but for now some important boot-time
-    options need /usr/bin/fs to set them.
+  * Update init script to require $remote_fs be started first and stopped
+    after OpenAFS.  This won't be the case in the long run, but for now
+    some important boot-time options need /usr/bin/fs to set them.
   * List $syslog in Should-Start for the openafs-client init script, since
     otherwise if loading the module causes a kernel panic, it won't be
     logged to disk.

diff --git a/debian/openafs-client.init b/debian/openafs-client.init
index 22fb1d172679e6fbc056488bfe2baf851b32ab5e..329cfca53a81ec9f09fd4d60c5a3085a33fc339d 100755 (executable)
--- a/debian/openafs-client.init
+++ b/debian/openafs-client.init
@@ -2,7 +2,7 @@
 ### BEGIN INIT INFO
 # Provides:             openafs-client
 # Required-Start:       $remote_fs $network $time
-# Required-Stop:        $network
+# Required-Stop:        $remote_fs $network
 # Should-Start:         $syslog
 # X-Stop-After:         autofs
 # Default-Start:        2 3 4 5