public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom H <tomh0665@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] NFS tutorial for the brain dead sysadmin?
Date: Sun, 27 Jul 2014 10:30:23 -0400	[thread overview]
Message-ID: <CAOdo=Sy_chND291NtKC4wNr-fosgb3nT68JMSUj3Nqw4D5O0dA@mail.gmail.com> (raw)
In-Reply-To: <53D3B279.6030906@gmail.com>

On Sat, Jul 26, 2014 at 9:51 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>
> NFS uses RPC to do some heavy lifting - I don't know how familiar you
> are with this, so here's the quick version:
>
> When you mount something locally, and need to use the mounted
> filesystem, kernel calls are used to get at the data. This works easily
> as the source disk is local and the kernel can get to it. With NFS, the
> source disk is remote and it's the remote kernel that must do the
> accessing. RPC is a way to safely ask a remote kernel to do something
> and get a result that behaves identical to a local kernel call.
> Obviously, this is rather hard to implement correctly.
>
> The original RPC was written by Sun and other newer implementations
> exist, like libtirpc - to support useful features like not being stuck
> with only UDP. That's what the "ti" means - Transport Independant.
>
> RPC has been in a state of flux for some time and I too have run into
> init-script oddities as things change.
>
> In my case, I have nfs-utils-1.3.0, and rc-update configuredd to start
> rpc.statd. This works because
>
> depend() {
>     ...
>     need portmap
>     ...
> }
>
> and in the init.d file for rpcbind:
>
> depend() {
>     ...
>     provide portmap
> }
>
> So rpcbind starts at boot time and all my nfs mounts JustWork

To confirm the above, for nfs-utils-1.2.9-r3.

If I start nfs manually, all the associated daemons start too even
though I haven't added them to "default" (although idmapd is started
because of "/etc/conf.d/nfs"):

# ls -1 /etc/init.d/rpc*
/etc/init.d/rpc.idmapd
/etc/init.d/rpc.pipefs
/etc/init.d/rpc.statd
/etc/init.d/rpcbind

# rc-update | grep rpc

# rc-service nfs start
 * Starting rpcbind ...                  [ ok ]
 * Starting NFS statd ...                [ ok ]
 * Setting up RPC pipefs ...             [ ok ]
 * Starting idmapd ...                   [ ok ]
 * Mounting nfsd filesystem in /proc ... [ ok ]
 * Exporting NFS directories ...         [ ok ]
 * Starting NFS mountd ...               [ ok ]
 * Starting NFS daemon ...               [ ok ]
 * Starting NFS smnotify ...             [ ok ]

#


  reply	other threads:[~2014-07-27 14:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26  2:47 [gentoo-user] NFS tutorial for the brain dead sysadmin? walt
2014-07-26 13:51 ` Alan McKinnon
2014-07-27 14:30   ` Tom H [this message]
2014-07-27 16:25 ` Stefan G. Weichinger
2014-07-27 16:55   ` J. Roeleveld
2014-07-27 19:44     ` Kerin Millar
2014-07-28 13:58       ` J. Roeleveld
2014-07-28 15:29         ` behrouz khosravi
2014-07-28 15:57           ` Neil Bothwick
2014-07-29  7:49             ` behrouz khosravi
2014-07-29  8:15               ` Peter Humphrey
2014-07-29  8:23                 ` behrouz khosravi
2014-07-27 17:07   ` Stefan G. Weichinger

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=Sy_chND291NtKC4wNr-fosgb3nT68JMSUj3Nqw4D5O0dA@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