Date: Mon, 5 Dec 2005 20:35:22 +0300 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> Cc: ports@freebsd.org, freebsd-rc@freebsd.org Subject: Re: RC keywords question Message-ID: <20051205173522.GC88485@comp.chem.msu.su> In-Reply-To: <20051205172658.GB88485@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051205173522.GC88485>