Date: Mon, 8 Feb 2010 17:46:23 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: George Mamalakis <mamalos@eng.auth.gr> Cc: freebsd-current@freebsd.org, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Kerberized NFSv3 incorrect behavior Message-ID: <Pine.GSO.4.63.1002081740530.17410@muncher.cs.uoguelph.ca> In-Reply-To: <4B704ECD.1060902@eng.auth.gr> References: <4B6BE7A2.6000402@eng.auth.gr> <Pine.GSO.4.63.1002051224510.27442@muncher.cs.uoguelph.ca> <4B6D3A18.2030304@eng.auth.gr> <Pine.GSO.4.63.1002071722390.5826@muncher.cs.uoguelph.ca> <4B704ECD.1060902@eng.auth.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 8 Feb 2010, George Mamalakis wrote:
>
> To tell you the truth, when I recompiled my kernel with:
>
> options NFSD
> options KGSSAPI
> device crypto
>
> to setup an nvsv4 server, nfsd refused to start because mountd was
> segfaulting. I didn't play much with this setup, because I was in a hurry, so
> I commented out NFSD and put back NFSSERVER, to be able to test my server.
>
Ok, I'll test the above case. It definitely should be fixed.
> Now a last question: Does gssapi/nfs setup work with the automounter
> (bsd/linux nfs-client)?
>
No idea. The Mac OS X client works ok with the automounter. The main
issue I'm aware of is that, if you are automounting home directories,
then the "kinit" has to happen before any access attempt to the home
dir. occurs during the login sequence. (I've never tried to automount
on either FreeBSD nor Linux.)
Have fun, rick
ps: The nfsv4@linux-nfs.org mailing list is a good place to ask, if
you run into Linux client issues.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1002081740530.17410>