I am currently adopting the orphaned autofs package. The issue you
reported here as something that we have been observing in Debian Edu
deployments for years. Thanks for proposing a fix.
On Wed, 26 Oct 2016 13:28:01 -0700 Daniel Lakeland
> Package: autofs
> Version: 5.1.1-1
> Severity: important
> Tags: patch
> Dear Maintainer,
> *** Reporter, please consider answering these questions, where
> appropriate ***
> * What led up to the situation?
> Boot machine that has autofs configured to mount directories under
> /home/ via nfs4.
> The machine comes up but directories don't get mounted.
> For this to work properly we need several things to happen:
> 1) rpc.idmapd and rpc.gssd need to run
> 2) autofs needs to start up after the network is online
> Add the following line to autofs.system
> Requires=network-online.target nfs-client.target
> Add the following line to nfs-client.target
> Requires=nfs-idmapd.service rpc-gssd.service
> After these changes, autofs starts up late enough that the network is
> online, and
> when it tries to mount nfs4 mounts it works
However, I suspect that we cannot entangle autofs and NFS as much as you
propose here. Note that people also may use autofs for local device
mounting and don't run NFS with it at all.
So, for the autofs side of things, I propose this (a Wants= solution
rather than a Requires= solution):
commit 9e1569ac32e53a6b364241fe68377579ffcbd5db (HEAD -> master)
Author: Mike Gabriel <mike.gabr...@das-netzwerkteam.de>
Date: Thu Mar 14 15:04:46 2019 +0100
debian/autofs.service: Add nfs-client.target to Wants= key.
Hopefully, this is sufficient to fix #842199, if not, please reopen the
bug. (Closes: #842199).
diff --git a/debian/autofs.service b/debian/autofs.service
index 8d7afa2..33a3d4e 100644
@@ -1,7 +1,7 @@
Description=Automounts filesystems on demand
After=network.target ypbind.service sssd.service network-online.target
You possibly may want to check, if that works as well. We will do heavy
testing here soon, too.