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 AB12F1388E5 for ; Wed, 29 Oct 2014 01:36:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9D191E097A; Wed, 29 Oct 2014 01:36:40 +0000 (UTC) Received: from mail-la0-f48.google.com (mail-la0-f48.google.com [209.85.215.48]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5C5EEE0919 for ; Wed, 29 Oct 2014 01:36:39 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id gq15so1729756lab.35 for ; Tue, 28 Oct 2014 18:36:37 -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=d6pTP9Rd6Jr+wLWHF64MR/3DgJOeskYwZK6nxPytEBc=; b=yCjon04hu3Q1eVsAk+YW7g77uXroOWK843e2mzILdjaEAoNCIeMuvyn8zO8EILwr3e a+d1hqMRJoUt7a4vWHV5GZf4yx4q8/S1GpKqwxDBeGvZ/bpnM9Is+/nYPhM+i8ouHvVa MQId7l0KYE09zVIRCvdk0yhMd3Ynsd+jfjHhqEUCfWI2YtSpG2acim9SjNip6dIrahlr ZgGTTdNIgmoS2xBwWZB7fKIJe0wBOMPyFtdJoX7vTiQmUlvgjP5n5vKI0J5g7APnJlqK AfHRBGxeC8zcvJzOSn/MW4BNjezx3qF+pBcrARxBYw+o9k+zMT8GHnJMSMLFctzUvmyU fFqQ== 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.22.74 with SMTP id b10mr7911504laf.16.1414546597607; Tue, 28 Oct 2014 18:36:37 -0700 (PDT) Received: by 10.152.22.168 with HTTP; Tue, 28 Oct 2014 18:36:37 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 Oct 2014 21:36:37 -0400 Message-ID: Subject: Re: [gentoo-user] Re: [~amd64] NFS server broken again :( From: Tom H To: Gentoo User Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 7db502ff-a584-4bb3-b5a1-066ac77aa9ef X-Archives-Hash: 8197312444ecc06d28928784b3895ec2 On Tue, Oct 28, 2014 at 6:18 PM, walt 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.