From owner-freebsd-ports@FreeBSD.ORG Mon Dec 5 17:35:32 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 25A4016A41F; Mon, 5 Dec 2005 17:35:32 +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 EDC0543D73; Mon, 5 Dec 2005 17:35:27 +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 jB5HZNvg090895; Mon, 5 Dec 2005 20:35:23 +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 jB5HZMjs090894; Mon, 5 Dec 2005 20:35:22 +0300 (MSK) (envelope-from yar) Date: Mon, 5 Dec 2005 20:35:22 +0300 From: Yar Tikhiy To: Ion-Mihai Tetcu Message-ID: <20051205173522.GC88485@comp.chem.msu.su> References: <20051205145805.0db6cf26@it.buh.tecnik93.com> <20051205161656.GC7653@odin.ac.hmc.edu> <20051205190905.28ad8a0a@it.buh.tecnik93.com> <20051205172658.GB88485@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051205172658.GB88485@comp.chem.msu.su> User-Agent: Mutt/1.5.9i Cc: 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: Mon, 05 Dec 2005 17:35:32 -0000 On Mon, Dec 05, 2005 at 08:26:58PM +0300, Yar Tikhiy wrote: > > > > > > "BEFORE: mail" acts for most intents and purposes like all mail > > > scripts contained "REQUIRE: dspam" so dspam does not depend on > > > LOGIN. As a rule, there's no point in depending on syslogd, just > > > > I think it's better if I make sure dspam starts before its potential > > consumers that the other way around; and this for one reason: I know > > that my port's consumers are mail servers, but making each mail server > > OPTIONally depend of each content filter is obviously unfeasible (of > > course I counld ask the user to modify his server's rc script by hand). > > Please correct me if I'm wrong. > > IMHO this is a very good general point. A mail server can live > without a content filter while the latter is meaningless without > the former. So the filter's rc.d script should use `BEFORE: mail'. Just a small clarification: I don't mean that the filter must start before mail. I mean that it is the filter's rc.d script that should contain the information for rcorder if any. OTOH, the mail rc.d script need not care about this issue at all. -- Yar