Le 13/12/2016 à 22:09, Andreas Henriksson a écrit : > I would suggest tagging these both as wontfix. Adding even more options > to the broken concept of /etc/default just adds to the maintenance burden > of having to carry this over via the nfs-utils_env.sh bridge. > > Both /etc/default/nfs-kernel-server and the init script are conffiles. > Edit them directly as you see fit to suite your installation if you're > still using this old stuff. They will not be overwritten on upgrades. > > On systemd there's a better concept of overriding settings so you don't > need to (and should avoid to) deal with /etc/default anymore. > > I suggest making the long-term goal to get rid of /etc/default. > Automatically handling conversion of users /etc/default over to proper > systemd style overrides would probably be a very fragile if not totally > impossible thing to accomplish though, so just adding NEWS entries > recommending users to manually convert their stuff over and removing > the files is probably the way to go.
Wontfix ? Really ? Are you that much intent on killing sysvinit ? Last time I checked, the Policy still required alternative init systems to be supported by package maintainers. Since it's so easy to override these settings with systemd (I'm not ironical here, I really don't know how it's done), what harm would this patch do if it was applied to satisfy sysvinit users ? They would have at last the possibility of modifying rpcnfsdopts through /etc/default/nfs-kernel-server, and thus reliably disable nfsv4, and systemd users could still do the same through whatever facility systemd provides and that I'm not aware of. Regards, -- Raphaël Halimi
signature.asc
Description: OpenPGP digital signature
