On 05/26/2016 11:22 AM, J. Bruce Fields wrote: >>>>> Idea 1: extra syntax in /etc/exports >>>> > >> >>>> > >> It's not really export-specific information. I wonder if it'd be better >>>> > >> to pass it on the rpc.nfsd commandline? >>>> > >> >>>> > >> rpc.nfsd --multipath-set="192.168.0.1,192.168.0.2" >>>> > >> >>>> > >> (and then that can be configured in /etc/sysconfig/nfs or whatever)? >> > >> > Is this (the rpc.nfsd command line and /etc/sysconfig/nfs entry) the >> > preferred way? >> > Is /etc/sysconfig/nfs read upon reboot? Again, I think this is just globing new stuff on old stuff... I'm just thinking having new commands to manage new technology better direction. > Yes. (Well, the details are distribution-dependent, I think it's up to > the /usr/lib/systemd/scripts/nfs-utils_env.sh script referenced in > nfs-utils/systemd/nfs-config.service.) These new command could have their very own system start up scripts > > The annoying thing about putting it on the rpc.nfsd commandline is that > it's mountd, not nfsd, that manages the NFSv4 pseudofs, and would be > responsible for cooking up the fs_locations info. I agree with this... structurally this just seems wrong. steved. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
