From owner-freebsd-current@FreeBSD.ORG Sun Aug 28 01:23:56 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E80B1065672 for ; Sun, 28 Aug 2011 01:23:56 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [204.109.58.86]) by mx1.freebsd.org (Postfix) with ESMTP id 0F3CD8FC0A for ; Sun, 28 Aug 2011 01:23:55 +0000 (UTC) Received: from meatwad.mouf.net (cpe-065-190-149-241.nc.res.rr.com [65.190.149.241]) (authenticated bits=0) by mouf.net (8.14.4/8.14.4) with ESMTP id p7S1NpVO075017 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 27 Aug 2011 21:23:54 -0400 (EDT) (envelope-from swills@FreeBSD.org) Message-ID: <4E5998A7.4080002@FreeBSD.org> Date: Sat, 27 Aug 2011 21:23:51 -0400 From: Steve Wills User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110531 Thunderbird/3.1.10 MIME-Version: 1.0 To: Rick Macklem References: <1653778001.444474.1314492943160.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1653778001.444474.1314492943160.JavaMail.root@erie.cs.uoguelph.ca> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mouf.net [204.109.58.86]); Sat, 27 Aug 2011 21:23:54 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.96.2 at mouf.net X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org Subject: Re: NFS mountd version 3 over TCP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 01:23:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/27/11 20:55, Rick Macklem wrote: >> I don't know why the nfsd wouldn't be able to bind(2) to port #2049 a >> second time for UDP, but someone on the net side might know? (Just in >> case it is a problem that has already been fixed, I'd try a newer kernel.) Will do, see below. >> The new server was broken by r224778 on Aug. 11 and fixed by r224911 on >> Aug. 16. (I recall you mentioning Aug. 11?) My kernel is from Aug 13, so definitely would fall into that range. I'll update and rebuild and see how it goes. Thanks! Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWZinAAoJEPXPYrMgexuhgp0H/1Dl9Bica8wbx5wLkkaPg5KM Rf53qdAgi/TarcMxufN+ujqx1EBu02hsSfB0vx8B0EZ9Ta1qWA/b2aL8SHJsXZFB gWPyr6sLINLcoaKGJ6Esp4QcIaU0PHOn4OhSGSMaZKYuMlXGsqJyJ3Wn6D46/4Re CbxioTfNT3c85x/khSE3nOCKsxKddKmM+VtuOloNRji969QlYH/1ZWItxbg6Tr1m hkT6v6hAM+EnvuLxlOJMTIegeec+WilIYSyP/FcuB2fcov1rdJSOOqOAUBHiBkRc uz3ADLr1QhwVue7sSA2PNDo3jQhtA7HFQKrEnIAW1xQFKuuapdgxr/wSDu2+T30= =5j1q -----END PGP SIGNATURE-----