From owner-freebsd-current@FreeBSD.ORG Wed Nov 12 23:40:33 2008 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 D73111065695 for ; Wed, 12 Nov 2008 23:40:33 +0000 (UTC) (envelope-from det135@psu.edu) Received: from f04n01.cac.psu.edu (f04s01.cac.psu.edu [128.118.141.31]) by mx1.freebsd.org (Postfix) with ESMTP id 89CF18FC1F for ; Wed, 12 Nov 2008 23:40:33 +0000 (UTC) (envelope-from det135@psu.edu) Received: from hoenikker.aset.psu.edu (hoenikker.aset.psu.edu [128.118.99.49]) by f04n01.cac.psu.edu (8.13.2/8.13.2) with ESMTP id mACF8p68121558; Wed, 12 Nov 2008 10:08:51 -0500 Received: from hoenikker.aset.psu.edu (hoenikker.aset.psu.edu [128.118.99.49]) by hoenikker.aset.psu.edu (8.14.2/8.14.2) with ESMTP id mACF8pVO030433; Wed, 12 Nov 2008 10:08:51 -0500 (EST) (envelope-from det135@hoenikker.aset.psu.edu) Received: (from det135@localhost) by hoenikker.aset.psu.edu (8.14.2/8.14.2/Submit) id mACF8p0f030432; Wed, 12 Nov 2008 10:08:51 -0500 (EST) (envelope-from det135) Date: Wed, 12 Nov 2008 10:08:50 -0500 From: Derek Taylor To: freebsd-current@freebsd.org Message-ID: <20081112150850.GC34909@psu.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: by amavisd-new Cc: dfr@freebsd.org Subject: Re: problems with nfsd (due to RPCSEC_GSS changes?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Derek Taylor List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 23:40:33 -0000 On Tue, 11 Nov 2008, Navdeep Parhar wrote: >Ultimately, I had to add NFS_LEGACYRPC in order to get a working nfsd. >Looks like there may be a problem with the new code that was added as >part of RPCSEC_GSS support. Note that I did not enable KGSSAPI in my >kernel as I have no need for it. It sounds like you were bitten by the behavior documented in paragraph two of the commit log: The NFS code currently contains support for both the new RPC implementation and the older legacy implementation inherited from the original NFS codebase. The default is to use the new implementation - add the NFS_LEGACYRPC option to fall back to the old code. When I merge this support back to RELENG_7, I will probably change this so that users have to 'opt in' to get the new code. -- Derek Taylor Applied Information Technologies Systems Design Specialist Pennsylvania State University det135@psu.edu 230J Computer Bldg Phone: +1 814 867 1533 University Park, PA, 16802