linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20230613034625.498132-1-github@aram.nubmail.ca> (raw)

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


             reply	other threads:[~2023-06-13  3:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  3:46 Aram Akhavan [this message]
2023-06-13  3:46 ` [PATCH 1/2] nfs-idmapd.service: add network-online.target to Wants= and After= Aram Akhavan
2023-06-13  3:46 ` [PATCH 2/2] 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 Aram Akhavan
2023-07-17 21:48 ` [PATCH 0/2] Mitigate startup race between DNS resolution and idmapd Steve Dickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230613034625.498132-1-github@aram.nubmail.ca \
    --to=github@aram.nubmail.ca \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).