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 468E11389FE for ; Fri, 31 Oct 2014 17:35:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 66C8CE090F; Fri, 31 Oct 2014 17:35:01 +0000 (UTC) Received: from mail-la0-f45.google.com (mail-la0-f45.google.com [209.85.215.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EE346E08EF for ; Fri, 31 Oct 2014 17:34:58 +0000 (UTC) Received: by mail-la0-f45.google.com with SMTP id pn19so1260690lab.18 for ; Fri, 31 Oct 2014 10:34:57 -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=tFCQYrIR15+8mUHhAByQGu3xmWMvOBD1RsoGyjX4ohU=; b=hbqUs5yUGaY+uhRU1OvSn8LyFa4Q2O5J0uAvCP8kZ5yLk7FzknDACYT1SLTXfgdjrJ Du7+opsrefPjQsqGIBgUOcp0L9G/28MLTGWroRrbgXv7OxYjw4AHurOOjXOj54Ck2l/a TdhYZEL0wHZOIdt3sKWjpCMlYzUtkUAOy2hPaB3P37xDFeghqqKupeK9/dTFQImVbme9 uMeIsT7kOghxxjFZ4d1kVnWxoZk7qqvrOT3cBeUDR/+wjFkTK9lc4JxCSRawMFdV3Lt9 2oqwlO2Tgt1Kg1oBosHyvTYZN8AHQVM6MEFZORuTHRivc346jfYDjY27uU8ygAiUPfcU DA8w== 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.234.167 with SMTP id uf7mr26315432lac.88.1414776897186; Fri, 31 Oct 2014 10:34:57 -0700 (PDT) Received: by 10.152.22.168 with HTTP; Fri, 31 Oct 2014 10:34:57 -0700 (PDT) In-Reply-To: References: Date: Fri, 31 Oct 2014 13:34:57 -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: be30c319-3c86-46cd-8182-7ee522d68afc X-Archives-Hash: 674dfd57a8288afa96b7595885e57ef7 On Tue, Oct 28, 2014 at 9:50 PM, Rich Freeman wrote: > On Tue, Oct 28, 2014 at 9:36 PM, Tom H wrote: >> 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. > > I was just looking at that and thinking the same thing. Nothing is > really forcing rpcbind to load the way things are specified right now. > If a service really requires another service to operate, it should say > that. There is no problem doing that via a target, but then the > target still needs to pull it in. Wouldn't the solution to this problem to have a news item to let the user know that rpcbind was being started as a dependency of nfsd.service but that it now needs to be enabled in order to be started by nfs-server.service? > There seems a general tendency in systemd to express dependencies as > "after" instead of "requires." That is fine if the service doesn't > really require something else, but if there really is a true > dependency then it just causes problems when somebody doesn't notice > and fails to enable the other unit. AFAIK they're completely different and you can have service1 have a "Requires" on service2 but have service2 start before service1. So if someone's using "After" and expecting "Requires", he/she is bound to be surprised by the result. Is "After" really necessary as an option? I've never come across a service that uses "After" without a "Requires" or a Wants" but I've never taken the time to look.