Re: [gentoo-user] Re: [~amd64] NFS server broken again :(

[Tom H <tomh0665@gmail.com>]

On Tue, Oct 28, 2014 at 6:18 PM, walt <w41ter@gmail.com> wrote:
> On 10/27/2014 08:22 PM, Tom H wrote:
>>
>> The 1.2.9 nfs-utils ebuild has "systemd_dounit
>> "${FILESDIR}"/nfsd.service" where nfsd.service has
>> "Requires=rpcbind.service" and "After=rpcbind.service".
>>
>> The 1.3.0 nfs-utils ebuild has "systemd_dounit
>> systemd/*.{mount,service,target}" where nfs-server.service has
>> "Requires=rpcbind.target" and After=rpcbind.target".
>
> Yes, and that little change caused the breakage that inspired this
> thread in the first place :)
>
> I have a Fedora 20 machine running in VirtualBox and I see they've
> already fixed the same breakage by going back to 'rpcbind.service'
> in their nfs-server.service file.
>
> I see they also define all those $RPCFOO variables in /etc/sysconfig/nfs,
> which are mostly null-strings anyway, which is why my nfs server is
> working correctly without those variables.
>
> (Working correctly *after* "systemctl enable rpcbind", that is.)

"systemctl enable rpcbind" or "systemctl start rpcbind"? (Or
"systemctl enable rpcbind" and reboot?)

I've been wondering about "rpcbind.target". I'm not using systemd on
Gentoo but on my laptop running Ubuntu 15.04 (yes, 15 with systemd
215), "/lib/systemd/system/rpcbind.target" is provided by systemd.
It's also part of the upstream tarball so it must be part of the
Gentoo package - and, I have to assume, part of the Fedora systemd
package since Lennart's its maintainer there.

Since Gentoo's rpcbind.service has "Wants=rpcbind.target" and
"Before=rpcbind.target"", having nfs-server.service depend on
rpcbind.target rather than rpcbind.service should work as long as
rpcbind.service is enabled.

But having "Requires=rpcbind.service" and "After=rpcbind.service",
like nfsd.service has/had, means that you don't have to enable
rpcbind.service.