From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [~amd64] NFS server broken again :(
Date: Tue, 28 Oct 2014 15:18:11 -0700 [thread overview]
Message-ID: <m2p4n5$qiv$1@ger.gmane.org> (raw)
In-Reply-To: <CAOdo=SyQ=Jb5-g=Uau1C1GKGYN0LXEaAXqvpg-MbHqPm5Wc5BQ@mail.gmail.com>
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.)
next prev parent reply other threads:[~2014-10-28 22:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:38 [gentoo-user] [~amd64] NFS server broken again :( walt
2014-10-27 19:56 ` Canek Peláez Valdés
2014-10-27 23:46 ` [gentoo-user] " walt
2014-10-28 1:05 ` Canek Peláez Valdés
2014-10-28 2:49 ` Tom H
2014-10-28 3:22 ` Tom H
2014-10-28 22:18 ` walt [this message]
2014-10-29 1:36 ` Tom H
2014-10-29 1:50 ` Rich Freeman
2014-10-31 17:34 ` Tom H
2014-10-31 18:27 ` Rich Freeman
2014-10-31 23:01 ` Tom H
2014-10-31 23:52 ` Rich Freeman
2014-11-03 1:37 ` Tom H
2014-11-03 3:47 ` Rich Freeman
2014-11-01 3:18 ` Jc García
2014-10-28 0:56 ` [gentoo-user] " Tom H
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='m2p4n5$qiv$1@ger.gmane.org' \
--to=w41ter@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox