From owner-freebsd-current Sat Jun 15 11:30:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from ns1.gnf.org (ns1.gnf.org [63.196.132.67]) by hub.freebsd.org (Postfix) with ESMTP id 9AC5837B401 for ; Sat, 15 Jun 2002 11:30:19 -0700 (PDT) Received: from mail.gnf.org (smtp.gnf.org [172.25.11.11]) by ns1.gnf.org (8.11.6/8.11.6) with ESMTP id g5FIU5X91308; Sat, 15 Jun 2002 11:30:05 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id 58A9E11E515; Sat, 15 Jun 2002 11:30:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 55D9B11A572; Sat, 15 Jun 2002 11:30:08 -0700 (PDT) Date: Sat, 15 Jun 2002 11:30:08 -0700 (PDT) From: Gordon Tetlow To: Terry Lambert Cc: Mike Makonnen , Danny Braniss , Subject: Re: HEADS UP: rc.d is in the tree In-Reply-To: <3D0A6E7B.F243329A@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 14 Jun 2002, Terry Lambert wrote: > Mike Makonnen wrote: > > Danny Braniss wrote: > > > in amd, > > > # REQUIRE: rpcbind mountall ypbind nfsclient > > > ****** > > > since i don't use yp, how can i override this? > > > > > > or in other words, can REQUIRE be configurable too? > > > > The REQUIRE line doesn't mean it will be started. It just means that > > ypbind comes before amd in the boot process. > > Ick. > > What should be used instead of REQUIRE to mean that it will be > started? > > I.e. if "REQUIRE" describes soft dependency ordering, what > describes hard dependency ordering? I don't like this design decision either. I have a couple of ideas on how to get rid of rcorder completely and bring the dependency checking into the script itself (complete with the notion of hard and soft dependencies). I was thinking of coming up with a way to make dynamic dependency registration and coming up with a reverse and forward dependency tree so if you stop nfsd, it would make a call to mountd to see if there was anything still using nfsd. If there weren't any more dependencies, it would then stop mountd (that could be a bit risky though, depending on the completeness of the dependency tree). -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message