On 3/3/21 1:10 PM, Chuck Lever wrote: > > >> On Mar 2, 2021, at 5:39 PM, Steve Dickson <SteveD@xxxxxxxxxx> wrote: >> >> >> >> On 2/24/21 3:49 PM, J. Bruce Fields wrote: >>> On Fri, Feb 19, 2021 at 03:08:08PM -0500, Steve Dickson wrote: >>>> nfsv4.exportd is a daemon that will listen for only v4 mount upcalls. >>>> The idea is to allow distros to build a v4 only package >>>> which will have a much smaller footprint than the >>>> entire nfs-utils package. >>>> >>>> exportd uses no RPC code, which means none of the >>>> code or arguments that deal with v3 was ported, >>>> this again, makes the footprint much smaller. >>>> >>>> The following options were ported: >>>> * multiple threads >>>> * state-directory-path option >>>> * junction support (not tested) >>>> >>>> The rest of the mountd options were v3 only options. >>>> >>>> V2: >>>> * Added two systemd services: nfsv4-exportd and nfsv4-server >>>> * nfsv4-server starts rpc.nfsd -N 3, so nfs.conf mod not needed. >>> >>> We really shouldn't make users change how they do things. >> If they only want v4 support... I'm thinking is a lot easier to >> simple do a nfsv4.server start verse edit config files. >> >>> >>> Whatever we do, "systemctl start nfs-server" should still be how they >>> start the NFS server. >> Again.. if they install the nfsv4-utils verse the nfs-utils package >> they should expect change... IMHO.. > > I would prefer having a single nfs-utils package. I don't see > a need for a proliferation of these extra little programs -- > let's just make the usual suspects behave better. nfs-utils is not going anywhere!! :-) I'm just trying to give people the option of only install a v4 client or v4 server. If they want it all... nfs-utils will be there!! steved.
