From 2e238eb10cd1c5206896728f89e3a8fa67ea66b7 Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Wed, 26 Nov 2014 12:58:10 -0500 Subject: [PATCH] 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. --- debian/changelog | 1 + debian/openafs-client.service | 1 + 2 files changed, 2 insertions(+) diff --git a/debian/changelog b/debian/changelog index 27c529f05..85af3c971 100644 --- 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 Thu, 06 Nov 2014 15:16:17 -0500 diff --git a/debian/openafs-client.service b/debian/openafs-client.service index ae290c9f2..2debcafcc 100755 --- 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 -- 2.39.5