FYI - this is now fixed upstream
Aram
On 5/10/2023 9:34 PM, Salvatore Bonaccorso wrote:
HI Aram,
On Wed, May 10, 2023 at 04:39:34PM -0700, Aram Akhavan wrote:
Yes. The issue still exists with nfs-common 2.6.2 (and the new libnfsidmap1
dependency). Not surprising since systemd unit in
HI Aram,
On Wed, May 10, 2023 at 04:39:34PM -0700, Aram Akhavan wrote:
> Yes. The issue still exists with nfs-common 2.6.2 (and the new libnfsidmap1
> dependency). Not surprising since systemd unit in question is the same. The
> fix for nfs-idmapd.service is a trivial two-line addition:
>
>
Yes. The issue still exists with nfs-common 2.6.2 (and the new
libnfsidmap1 dependency). Not surprising since systemd unit in question
is the same. The fix for nfs-idmapd.service is a trivial two-line addition:
Wants=network-online.target
After=network-online.target
I recall a comment
On Wednesday, 10 May 2023 04:29:10 CEST Aram Akhavan wrote:
> Package: nfs-common
> Version: 1:1.3.4-6
We're currently at version 2.6.2 (or .3 in experimental) and I doubt that
upstream cares about version 1.3.4.
Can you reproduce the issue with version 2.6.2 (or higher)?
signature.asc
Package: nfs-common
Version: 1:1.3.4-6
Severity: important
Tags: upstream
X-Debbugs-Cc: deb...@aram.nubmail.ca
Dear Maintainer,
The nfs-idmapd.service included in nfs-utils does not wait for the
network to start. If DNS resolution is not yet available, and no domain
is explicitly set up in the
5 matches
Mail list logo
