Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
To:     "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
From:   Doug Nazar <nazard@nazar.ca>
Subject: nfs-utils README updates
Message-ID: <34f07da7-250d-f354-bf59-74b9f1a0e16f@nazar.ca>
Date:   Thu, 16 Jul 2020 17:36:52 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101
 Firefox/78.0 Thunderbird/78.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

I was looking through the README to ensure my systems followed the 
correct setup and noticed a few things.

Looks like the reference to libnfsidmap can be dropped.

It looks like nfsdcld is again the correct setup for client tracking. A 
section should be added to SERVER STARTUP to include nfsdcld on NFS4+ 
servers.

Should it mention which modules are required before starting? I've had 
to locally add 'auth_rpcgss' to my startup scripts or svcgssd will bail 
on startup.

Any other changes or best practices that should be mentioned before I 
send a patch?

Thanks,
Doug