Date: Tue, 03 Jul 2001 09:44:46 -0600 From: Wes Peters <wes@softweyr.com> To: David Terrell <dbt@meat.net> Cc: Cyrille Lefevre <clefevre@redirect.to>, freebsd-hackers@FreeBSD.ORG Subject: Re: import NetBSD rc system Message-ID: <3B41E86E.AED9E1D3@softweyr.com> References: <lmmvoq3r.fsf@gits.dyndns.org> <Pine.BSF.4.33.0106131750560.94127-100000@sdmail0.sd.bmarts.com> <20010613202415.A3689@core.usrlib.org> <4rtjnv83.fsf@gits.dyndns.org> <20010702152646.B11363@pianosa.catch22.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David Terrell wrote:
>
> On Thu, Jun 14, 2001 at 01:42:36PM +0200, Cyrille Lefevre wrote:
> > in fact, the require keyword isn't sufficient in it's own. there
> > should be pre_require and post_require keywords since nfsd needs to
> > start mountd before to start nfsd then rpc.statd and rpc.lockd have to
> > be started after nfsd.
>
> Sorry to jump in an old discussion, I don't read fbsd-hackers often
> enough, apparently.
>
> In this situation, wouldn't you rather take the solaris option of
> putting "nfs_servers" in their own startup option and start the
> servers desired (maybe you don't want rpc.lockd) according to normal
> rc.conf knobs. For services as tightly coupled as this that seems
> like a much better way of guaranteeing ordering, and the whole package
> could then depend on portmap.
>
> It's not like you'd ever want nfsd and not mountd, or vice versa.
That's easy enough to do. With processes that are intrinsically linked like
nfs and mountd, you start them from the same script. For services that are
linked only by requirement, like nfs serving vs. rpc, you use the dependency
controls. Nobody said the NetBSD rc system removed the need for programmers
to think.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B41E86E.AED9E1D3>