From owner-freebsd-current@FreeBSD.ORG Sat Aug 27 13:40:38 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 4BD911065670 for ; Sat, 27 Aug 2011 13:40:38 +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 086398FC17 for ; Sat, 27 Aug 2011 13:40:37 +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 p7RDea5I072207 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 27 Aug 2011 09:40:37 -0400 (EDT) (envelope-from swills@FreeBSD.org) Message-ID: <4E58F3D4.6070809@FreeBSD.org> Date: Sat, 27 Aug 2011 09:40:36 -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: <1032633878.435433.1314450034816.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1032633878.435433.1314450034816.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 09:40:37 -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: Sat, 27 Aug 2011 13:40:38 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/27/11 09:00, Rick Macklem wrote: >> This line indicates that mountd over tcp is registered for v3, >> so I suspect the error message is misleading?? Forgot to reply to this part, and I should have been more clear earlier. When I used the default nfsd flags, it failed to startup, or exited immediately on startup (not sure which). When I removed -u flag, it started up and that message was replaced with the one about fsinfo timeout. I can get the exact error message and tcpdump if you like. I then added -o flag to nfsd (didn't put -u back) and then things seemed to work OK. Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOWPPUAAoJEPXPYrMgexuhrLIH/jpRbAaKde9qi3xzsiIaZsuI +O31ScAk+weud90cEjf/N9PwW5PfSJYHMO03hliMVGuOphkwYnpN2AStExzScfmm nCFLz5UpzeKjznzirSOSNCGqwAyN3aPrghlyqNNi5eSkM9s0BdJgKBd+H9oSk7JE 7rf83Q2kPdqfvwhvRNpImC5oEXkZpExmitoIhESdnI/asr5OBwHIh8HthgIgMx+o 0t7v+togz0dT2jR7D+U1QbKhH5QP8pamjpP80D4TsO8P9pGt/PUuSBQAwDfQ3pjf Tjnc2t9YMQ+hw3zqYTRrNCNMvaH7PlyAW0LvuW1Nhk8mus6HFxP1St/hgko+Y+8= =Pdq4 -----END PGP SIGNATURE-----