Date: Thu, 10 Mar 2011 08:49:04 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: George Mitchell <george+freebsd@m5p.com>, freebsd-stable@freebsd.org Subject: Re: statd/lockd startup failure Message-ID: <E1PxZgG-0007EI-5r@kabab.cs.huji.ac.il> In-Reply-To: <1139116164.1119047.1299711816326.JavaMail.root@erie.cs.uoguelph.ca> References: <1139116164.1119047.1299711816326.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > Thanks for the analysis. The reason I originally posted is to see why > > this might have popped up in 8.x, as it never happened in 7.x. > > -- George Mitchell > > > I suspect two things make this occur more frequently with 8.x. One is > that it does IPv6 first (I suspect IPv6 wasn't enabled by default on 7.x?). > > The other is the port randomization code, which probably results in > more frequent collisions with port #s used by other things. (Basically, > the code selects an unused port# for either UDP or TCP over IPv6 (I can't > remember which comes first:-) and then expects that port to be available > for the other 3 combinations of UDP/TCP x IPv6/IPv4. anothere reason for it is probably the multy-cores, most of these daemons fork very early, and very quickly are compiting for resources in parallel. danny PS: rick, can you send me your patch?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1PxZgG-0007EI-5r>