From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C5EDF1391DB for ; Sun, 27 Jul 2014 14:30:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4F07EE0B90; Sun, 27 Jul 2014 14:30:26 +0000 (UTC) Received: from mail-la0-f66.google.com (mail-la0-f66.google.com [209.85.215.66]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 09FB9E099C for ; Sun, 27 Jul 2014 14:30:24 +0000 (UTC) Received: by mail-la0-f66.google.com with SMTP id mc6so1502986lab.1 for ; Sun, 27 Jul 2014 07:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ODSYfRSig693UlwZ/vBwekGIWCalSwjKaf3csn87sN4=; b=No/5f2OuWfji0h4jUP/rWNWVEakvwuuAn2CK1tR1Hbzl2V7gmqZTxJ3i5QAVGYUmCS pmeQBadOwGRtLS5pl2Cr17J7meMVBIrEw3y6vVUwYB99++pgbDk2a7NYt8/3PzbYmAG3 qhyfPQwZiO3aoSgMLvi+O31ur/D1aZ9673EogioliRCoDA0vOF02OcvGCUhJexBugCjU vshkfL9zks5BX9iQXVvBoyoy1Lio77srF46n6wEhZznj9H/GDtQX4zqq5G1se67BTznc IljbX9UHuU0anM/Wv1HEwwIRF81YUHRHcAe15CT+B9a4g5m5Z4ZkvNvj6ITAuMZmxTGM SP1g== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.152.19.65 with SMTP id c1mr2549705lae.88.1406471423173; Sun, 27 Jul 2014 07:30:23 -0700 (PDT) Received: by 10.152.36.136 with HTTP; Sun, 27 Jul 2014 07:30:23 -0700 (PDT) In-Reply-To: <53D3B279.6030906@gmail.com> References: <53D3B279.6030906@gmail.com> Date: Sun, 27 Jul 2014 10:30:23 -0400 Message-ID: Subject: Re: [gentoo-user] NFS tutorial for the brain dead sysadmin? From: Tom H To: Gentoo User Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 87d1b2e8-b216-41f8-9833-f6d1a90ef8be X-Archives-Hash: 6eaaf71a03fd7f1f891e7074a2bafbdd On Sat, Jul 26, 2014 at 9:51 AM, Alan McKinnon 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 ] #