openafs-client should RemainAfterExit

Otherwise, if the options are such that there are no userland threads
that stick around (as would happen for -afsdb), systemd thinks that
we have finished, and runs the stop commands right away.

Thanks to Andrew Deason for noticing the issue at upstream.

diff --git a/debian/changelog b/debian/changelog
index 27c529f051a82289b66821a2fc88d1a643fd43ca..85af3c971e32b7e2ed6433f66eb7ce2cf3458a2a 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,7 @@ openafs (1.6.10-3) UNRELEASED; urgency=medium
 
   * Make openafs-client Before=umount.target for improved shutdown
     behavior. (Affects: #760063)
+  * Mark openafs-client.service as RemainAfterExit=true. (Closes: #770815)
 
  -- Benjamin Kaduk <kaduk@mit.edu>  Thu, 06 Nov 2014 15:16:17 -0500
 

diff --git a/debian/openafs-client.service b/debian/openafs-client.service
index ae290c9f2494b07c4265001e6c8a39d276d4c8df..2debcafccd641cbc9617fd8b8260b3427a9f65e7 100755 (executable)
--- a/debian/openafs-client.service
+++ b/debian/openafs-client.service
@@ -6,6 +6,7 @@ Before=remote-fs.target umount.target
 
 [Service]
 Type=forking
+RemainAfterExit=true
 ExecStartPre=/usr/share/openafs/openafs-client-precheck
 ExecStart=/sbin/afsd $AFSD_ARGS
 ExecStartPost=/usr/bin/fs setcrypt $AFS_SETCRYPT