From owner-freebsd-ports@FreeBSD.ORG Tue Dec 6 05:14:00 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEF2E16A41F; Tue, 6 Dec 2005 05:14:00 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0453243D68; Tue, 6 Dec 2005 05:13:52 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id jB65DkcG031393; Tue, 6 Dec 2005 08:13:46 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id jB65DUsq031387; Tue, 6 Dec 2005 08:13:30 +0300 (MSK) (envelope-from yar) Date: Tue, 6 Dec 2005 08:13:30 +0300 From: Yar Tikhiy To: Brooks Davis Message-ID: <20051206051329.GA30433@comp.chem.msu.su> References: <20051205145805.0db6cf26@it.buh.tecnik93.com> <20051205161656.GC7653@odin.ac.hmc.edu> <20051205171416.GA88485@comp.chem.msu.su> <20051205220053.GB24743@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051205220053.GB24743@odin.ac.hmc.edu> User-Agent: Mutt/1.5.9i Cc: Ion-Mihai Tetcu , ports@freebsd.org, freebsd-rc@freebsd.org Subject: Re: RC keywords question X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 05:14:01 -0000 On Mon, Dec 05, 2005 at 02:00:53PM -0800, Brooks Davis wrote: > On Mon, Dec 05, 2005 at 08:14:16PM +0300, Yar Tikhiy wrote: > > Just an additional remark: > > > > In a system with complex interactions it can be hard to order rc.d > > scripts properly without help from services they start. For instance, > > the database can REQURE "mail". Then either the mail daemon should > > spool mail until dspam starts after the database, or dspam should > > start early and return a temporary failure condition to the mail > > daemon until it can connect to the database. Similar considerations > > apply to other practical cases. > > Loops are definitely something to be watched out for, but this one is > a somewhat poor example, IMO. Looking at the "mail" scripts in the > base, it's clear that they are intended to provide the local delivery > agent. If the particular mail system needs daemons running for local > mail submission to work, those daemons must start much earlier (probably > BEFORE: SERVERS). Have you ever met lame software trying to send mail about its condition directly by SMTP to a pre-set local relay? So a database engine can, in theory, requre "mail". Of course, I won't advise using such a bogus DB engine, but my example isn't too poor either ;-) -- Yar