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.
signature.asc
Description: PGP signature
