From: Tom H <tomh0665@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: [~amd64] NFS server broken again :(
Date: Mon, 27 Oct 2014 23:22:43 -0400 [thread overview]
Message-ID: <CAOdo=SyQ=Jb5-g=Uau1C1GKGYN0LXEaAXqvpg-MbHqPm5Wc5BQ@mail.gmail.com> (raw)
In-Reply-To: <CAOdo=Swq5hLahkpnHV+5ADTaJaeBjrzqUTjiD4wQiKrAQfKgwQ@mail.gmail.com>
On Mon, Oct 27, 2014 at 10:49 PM, Tom H <tomh0665@gmail.com> wrote:
> Does rpcbind.target exist? Does rpcbind.service have a "Requires" or
> "Wants" for rpcbind.target? Is rpcbind.service enabled?
...
> I don't have access to a Gentoo box with nfs at the moment in order to
> check this but IIRC Gentoo used to use OPTS_RPC_NFSD, OPTS_RPC_MOUNTD,
> OPTS_RPC_STATD but it's now using upstream's RPCNFSDARGS,
> RPCMOUNTDARGS, STATDARGS, at least in its systemd units. Again IIRC
> the ebuild only changes the upstream "EnvironmentFile=" value and
> deep-sixes nfs-config.service.
I've just had the unoriginal idea of looking at my portage tree's
nfs-utils and rpcbind ebuilds and files...
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".
The rpcbind ebuild has "systemd_dounit "${FILESDIR}"/${PN}.service" so
there's no "${PN}.target" (and there isn't a ".target" unit in
$FILESDIR).
And, I was wrong:
cat $FILESDIR/nfs.confd
# /etc/conf.d/nfs
# If you wish to set the port numbers for lockd,
# please see /etc/sysctl.conf
# Optional services to include in default `/etc/init.d/nfs start`
# For NFSv4 users, you'll want to add "rpc.idmapd" here.
NFS_NEEDED_SERVICES=""
# Number of servers to be started up by default
OPTS_RPC_NFSD="8"
# Options to pass to rpc.mountd
# ex. OPTS_RPC_MOUNTD="-p 32767"
OPTS_RPC_MOUNTD=""
# Options to pass to rpc.statd
# ex. OPTS_RPC_STATD="-p 32765 -o 32766"
OPTS_RPC_STATD=""
# Options to pass to rpc.idmapd
OPTS_RPC_IDMAPD=""
# Options to pass to rpc.gssd
OPTS_RPC_GSSD=""
# Options to pass to rpc.svcgssd
OPTS_RPC_SVCGSSD=""
# Options to pass to rpc.rquotad (requires sys-fs/quota)
OPTS_RPC_RQUOTAD=""
# Timeout (in seconds) for exportfs
EXPORTFS_TIMEOUT=30
# Options to set in the nfsd filesystem (/proc/fs/nfsd/).
# Format is <option>=<value>. Multiple options are allowed.
#OPTS_NFSD="nfsv4leasetime=30 max_block_size=4096"
so if you're using the 1.3.0 nfs-utils ebuild, you have to set up the
variables yourself, if you need to pass different values to the
daemons.
next prev parent reply other threads:[~2014-10-28 3:22 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 [this message]
2014-10-28 22:18 ` walt
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='CAOdo=SyQ=Jb5-g=Uau1C1GKGYN0LXEaAXqvpg-MbHqPm5Wc5BQ@mail.gmail.com' \
--to=tomh0665@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