Date: Sun, 24 Apr 2011 08:42:54 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Kostik Belousov <kostikbel@gmail.com> Cc: rc@freebsd.org, Doug Barton <dougb@freebsd.org> Subject: Re: rc scripts change for review Message-ID: <1851380373.487655.1303648974162.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20110424122426.GF48734@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sun, Apr 24, 2011 at 08:05:04AM -0400, Rick Macklem wrote:
> > One possible explanation here (and it may be that I haven't set the
> > modules/sysctl stuff up correctly?) is that the "nfsd" module
> > depends
> > on the module "nfscommon" (which is loaded when nfsd is loaded,
> > because
> > of a MODULE_DEPEND() in "nfsd"). The SYSCTL_NODE() is in
> > "nfscommon".
> > I only have a SYSCTL_DECL() in "nfsd". (ie. maybe kldload doesn't
> > wait
> > for "nfscommon" to be loaded.)
> >
> > I just tried:
> > load_kld nfscommon
> > load_kld nfsd
> > - and this works without needing "nfssrv"
> >
> > I'm not sure if the above implies a bug in either my server code or
> > the module loading/sysctl registering stuff, but I'm confortable
> > with
> > doing the 2 load_kld's.
>
> Dependencies are loaded synchronously too.
Hmm, in this case I think "nfscommon" is linked into the kernel, since
it is used by the client as well and the client is linked in.
Does that affect the outcome? rick
ps: I'll build a kernel without the client linked in and see if that
makes a difference.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1851380373.487655.1303648974162.JavaMail.root>