From 49bf5d8df1106ad1c85d02ffc3d6f5a0335c539b Mon Sep 17 00:00:00 2001 From: "Darrick J. Wong" Date: Tue, 14 Apr 2020 12:56:20 -0400 Subject: [PATCH] xfs_scrub: don't set WorkingDirectory= in systemd job Somewhere between systemd 237 and 245, they changed the order in which a job has its uid/gid set; capabilities applied; and working directory set. Whereas before they did it in an order such that you could set the working directory to a path inaccessible to 'nobody' (either because they did it before changing the uid or after adding capabilities), now they don't and users instead get a service failure: xfs_scrub@-boot.service: Changing to the requested working directory failed: Permission denied xfs_scrub@-boot.service: Failed at step CHDIR spawning /usr/sbin/xfs_scrub: Permission denied xfs_scrub@-boot.service: Main process exited, code=exited, status=200/CHDIR Regardless, xfs_scrub works just fine with PWD set to /, so remove that directive. Signed-off-by: Darrick J. Wong Reviewed-by: Eric Sandeen Signed-off-by: Eric Sandeen --- scrub/xfs_scrub@.service.in | 1 - 1 file changed, 1 deletion(-) diff --git a/scrub/xfs_scrub@.service.in b/scrub/xfs_scrub@.service.in index 56acea671..6fb3f6ea2 100644 --- a/scrub/xfs_scrub@.service.in +++ b/scrub/xfs_scrub@.service.in @@ -5,7 +5,6 @@ Documentation=man:xfs_scrub(8) [Service] Type=oneshot -WorkingDirectory=%I PrivateNetwork=true ProtectSystem=full ProtectHome=read-only -- 2.49.0