Mitigate startup race between DNS resolution and idmapd
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | nfs-idmapd.service: add network-online.target to Wants= and After=systemd/ | +2 | 0 replies | |
| 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 determinedsupport/ | +10 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Mitigate startup race between DNS resolution and idmapd
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(-)
Signature · 1 line
2.39.2