[PATCH 0/2] Mitigate startup race between DNS resolution and idmapd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux