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 20BFE1389FE for ; Fri, 31 Oct 2014 23:01:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D7956E0944; Fri, 31 Oct 2014 23:01:45 +0000 (UTC) Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 705B9E0907 for ; Fri, 31 Oct 2014 23:01:44 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id z12so6721948lbi.25 for ; Fri, 31 Oct 2014 16:01:42 -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=KIR5HbECRdNMUtdsLC87fZRa1EGq3+6YDwfj/0MkgSU=; b=HEik4Uh9cFipkYf/1DX0O/evSAnta/Netv7xFzi2A+KE0aP2ZAkAffDIdhIPLO4chy rV6hErDn7nb6maTxtOoTaWayPc4ZJYW9d+SrQFF5Jt+VcKIFRk68qcPt/429dyCK2dgM wKkXGLzBVFsCjBQQ0bHoR+946jWek3+WTJPhFYcRZrTTwFTHrQ46gIX1FiFZ0xYm4Kcs dXjcTz9l/pNSxkaGywSptWWhp3PKRPP9kgOc12Bf6UwY5WM3I3XXRUYZ1r/8biNjgRUv 0i1LZWskVk10uQYs5lnvALpT8ypfWiBYwmSLE+VGNWfC/rxZtl1Ls6GWJOLHJCIqPdgO kHWg== 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.227 with SMTP id uh3mr29775052lac.69.1414796502732; Fri, 31 Oct 2014 16:01:42 -0700 (PDT) Received: by 10.152.22.168 with HTTP; Fri, 31 Oct 2014 16:01:42 -0700 (PDT) In-Reply-To: References: Date: Fri, 31 Oct 2014 19:01:42 -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: bcdd49df-bb65-483b-aa05-e270495dff14 X-Archives-Hash: 9196eeb360d0445da3e7708323acead3 On Fri, Oct 31, 2014 at 2:27 PM, Rich Freeman wrote: > On Fri, Oct 31, 2014 at 1:34 PM, Tom H wrote: >> 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. > > Hmm, I found After more common that Wants, but maybe I only look at > units that have problems. :) LOL. Which supports the thesis that "After" might not be a useful setting within a service unit. But it's just occured to me that target units use "After" without "Requires" or "Wants", for example network-online.target has "After=network.target". > I think the intent is to handle optional dependencies, but in practice > I don't know that it works well. It would almost be better to have > some kind of cluster config file that specifies all the actual > dependencies (possibly including cross-host) and have it spit out all > the unit dependencies automatically. That is a bit much to ask for > now, and probably a bit much for somebody who just wants their laptop > to launch kde after all their mounts are ready. Optional dependencies are handled by "Wants" like openrc's "use". IIUC you're referring to a BSD-like rc daemon config file. WOuldn't that have to be maintained by a sysadmin rather than by a package maintainer? > Specifying After vs Wants separately does make sense. Dependency > doesn't have to imply sequential. Do you have an example of a service that uses "After=" but doesn't need a "Requires=" or a "Wants="? I'm either being unimaginative or plain dumb, but I can't think of any. I wonder whether, if Lennart and co removed "After=" from service units and turned "Requires=" into the equivakent of the current "Requires=" and "After=" setup, someone would raise a storm over the change because it would've broken something.