Robbie Harwood: > Niels Thykier <ni...@thykier.net> writes: > >> NeilBrown: >>> On Sun, Mar 05 2017, Daniel Pocock wrote: >>> >>> The systemd unit files are designed so that svcgssd will only be >>> started if gssproxy didn't start - and gssproxy is tried first. >>> >>> If you use something other than systemd, similar logic would be >>> needed. >> >> @Robbie: Can you clarify what happens for people who have chosen to >> use sysvinit as init system? Will they end up with gssproxy or >> svcgssd or a broken NFS? > > I don't totally understand these unit files, so this is probably a > better question for the NFS folk. But: > > The gssproxy package contains a sysvinit script, which works just fine > on my sysvinit system. (And I assume on systemd systems due to lack of > bug reports :) ) > > Since nfs-common doesn't provide sysvinit scripts as far as I can tell, > I think you already can't run any of this on them, unless I'm missing > something. > > So you'd get gssproxy, and no NFS, but that was already the case. >
Ok - as I understand it, what we are dealing with here is: * systemd: You can get gssproxy + NFS and it "just works(tm)" if you install gssproxy. Otherwise you get svcgssd + NFS. (This is how I understood Neil Brown) * sysvinit: Business as usual either way. So granting gssproxy will: * Provide systemd users with NFS + gssproxy if they opt-in to it (by installing it) * Provide sysvinit users gssproxy and if they want to use it with NFS, they may have to tweak things themselves * Not cause any issues for neither systemd users nor sysvinit users just by installing it. * enable users to get gssproxy which is not deprecated (unlike the existing svcgssd) Is the above correct? And you are happy with gssproxy/0.5.1-2 as it is? If we are going to grant an exception, we will do so under the assumption that it "just works" and it won't case issues. If that assumption turns out to be false, I will sooner undo this exception and remove gssproxy than I will be spending time reviewing additional unblock requests for it. Thanks, ~Niels