Re: Must statd be running before nfs client makes mounts?

["H. J. Lu" <hjl@lucon.org>]

On Mon, Sep 16, 2002 at 10:00:11AM +1000, Neil Brown wrote:
> On Sunday September 15, hjl@lucon.org wrote:
> > On Mon, Sep 16, 2002 at 09:26:21AM +1000, Neil Brown wrote:
> > > 
> > >   (start devices, raid, etc)
> > >  1/ mount local filesystems
> > >   (start network, bind, portmap)
> > 
> > I am thinking to write a kernel patch to set nlm_udpport and
> > nlm_tcpport. The current scheme works only with module and /proc
> > won't work with module. I'd like to be able to set ports used by
> > lockd according to /etc/services. In my case, I have
> > 
> > nlockmgr        3003/tcp
> > nlockmgr        3003/udp
> > 
> > But I have to hard code them in my kernel.
> 
> You shouldn't need to hard code them,  kernel parameters:
>    lockd.udpport=3003 lockd.tcpport=3003
> should work fine (unless that is what you mean by hardcoding)

It is still hardcoding since can't change it at runtime.

> 
> However I don't see a problem with doing this via a sysctl, quite
> possibly a sysctl under /proc/sys/sunrpc/  (as it is an RPC service).
> 

Does it work with sunrpc as module?


H.J.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs