From: Steve Dickson <steved@redhat.com>
To: Aram Akhavan <github@aram.nubmail.ca>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] Mitigate startup race between DNS resolution and idmapd
Date: Mon, 17 Jul 2023 17:48:13 -0400 [thread overview]
Message-ID: <fd91b129-b383-9b1d-0978-032a7ff92dbb@redhat.com> (raw)
In-Reply-To: <20230613034625.498132-1-github@aram.nubmail.ca>
On 6/12/23 11:46 PM, Aram Akhavan wrote:
> 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(-)
>
Both committed... (Tag nfs-utils-2-6-4-rc3)
steved
prev parent reply other threads:[~2023-07-17 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 3:46 [PATCH 0/2] Mitigate startup race between DNS resolution and idmapd Aram Akhavan
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 ` Steve Dickson [this message]
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=fd91b129-b383-9b1d-0978-032a7ff92dbb@redhat.com \
--to=steved@redhat.com \
--cc=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).