Hi So conclusive, as explained by upstream:
1. the nfsdctl error is harmless, and if nfs-utils used with kernel which does not support the netlink control interfaces for knfsd then falls back to start the server with rpc.nfsd and this is indeed the case. 2. the previous starting with nfsdctl autostart was actually a regression now fixed with 2.8.3, since older nfsdctl just ingored the lockd parameters in nfs.conf nd would not have configured it properly so technically a regression from 1:2.6.2-4+deb12u1 in bookworm to the 2.8.2 based version previously, and now fixed in 2.8.3. Closing thus the issue. Regards, Salvatore
