statd/lockd startup failure

Rick Macklem rmacklem at uoguelph.ca
Fri Mar 11 23:03:43 UTC 2011


> >> On 02/18/2011 10:08, Rick Macklem wrote:
> >> > The attached patches changes the behaviour so that it tries to
> >> > get an unused port for each of the 4 cases.
> >>
> >> can you send me the patches?
> >> thanks,
> >> danny
> 
> > They're attached. If you get to test them, please let me know
> > how it goes.
> >
> > rick
> 
> Hi Rick,
> the good side of living on different time zones :-)
> I got impatient, so I came up with a different fix.
> The rational is that IMHO, there is no need for all listeners
> to be on the same port:
> rnd> rpcinfo protonew |grep mountd
> 100005 1 udp6 ::.3.141 mountd superuser
> 100005 3 udp6 ::.3.141 mountd superuser
> 100005 1 tcp6 ::.3.141 mountd superuser
> 100005 3 tcp6 ::.3.141 mountd superuser
> 100005 1 udp 0.0.0.0.3.141 mountd superuser
> 100005 3 udp 0.0.0.0.3.141 mountd superuser
> 100005 1 tcp 0.0.0.0.3.92 mountd superuser <---
> 100005 3 tcp 0.0.0.0.3.92 mountd superuser <---
> rnd> rpcinfo -t protonew mountd
> program 100005 version 1 ready and waiting
> rpcinfo: RPC: Program/version mismatch; low version = 1, high version
> = 3
> program 100005 version 2 is not available
> program 100005 version 3 ready and waiting
> 
> the patches are in:
> ftp://ftp.cs.huji.ac.il/users/danny/freebsd/patches/address_already_in_use/
> 
> cheers,
> danny
> 
Yep, a patch that doesn't make them all use the same port# is much
simpler. However, others, such as Doug Barton feel that it is important
that they use the same port#. (Something he called "tracking".)

rick


More information about the freebsd-stable mailing list