Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: i8ce9446d:Fastmail
From:   Aram Akhavan <github@aram.nubmail.ca>
To:     linux-nfs@vger.kernel.org
Cc:     Aram Akhavan <github@aram.nubmail.ca>
Subject: [PATCH 0/2] Mitigate startup race between DNS resolution and idmapd
Date:   Mon, 12 Jun 2023 20:46:23 -0700
Message-Id: <20230613034625.498132-1-github@aram.nubmail.ca>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

idmapd needs DNS resolution on startup if a domain isn't specified by
config file. This isn't trivial since even with systemd's
network-online.target, DNS resolution isn't guaranteed. On Debian,
for example (in part due to some lingering bugs), adding the
target, and even enabling the not-well-documented
ifupdown-wait-online.service is not enough. These two patches aim to
improve the startup behavior in common setup scenarios.

Aram Akhavan (2):
  nfs-idmapd.service: add network-online.target to Wants= and After=
  libnfsidmap: try to get the domain directly from hostname if the DNS
    lookup fails and always show the log message if the domain can't be
    determined

 support/nfsidmap/libnfsidmap.c | 15 ++++++++++-----
 systemd/nfs-idmapd.service     |  3 ++-
 2 files changed, 12 insertions(+), 6 deletions(-)

-- 
2.39.2