Date: Wed, 31 Dec 2008 10:26:36 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Bryan Alves <bryanalves@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: NFS locking problems with 7.0-RELEASE Message-ID: <alpine.BSF.2.00.0812311021590.41786@fledge.watson.org> In-Reply-To: <92f477740812302109n78d9f303y5c49b8ca6ab082c5@mail.gmail.com> References: <92f477740812291739o7c0b840bsd1cce4375577c41f@mail.gmail.com> <6eb82e0812301247uaf5eb45v529765e29220fd80@mail.gmail.com> <92f477740812302109n78d9f303y5c49b8ca6ab082c5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 31 Dec 2008, Bryan Alves wrote: > Where can I find more information about in kernel NFS_LOCKD? It doesn't > seem to exist on google at all, and I'm hesistant to upgrade from RELEASE > without doing due dilligence in terms of research. I'm not sure there's a specific web page/etc on it, but you can find the initial patch announcement here: http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084446.html I believe the "-k" described in the original post is no longer required. > Is rpc.lockd_enable still required in rc.conf when using this? Hmm. I believe so. > Do I need to do anything else besides update to RELENG_7 and > installworld/installkernel with this new option? You can do the normal upgrade -- build world, kernel, install kernel, reboot, mergemaster -p, installworld, full mergemaster, reboot. Or you can wait another week and install FreeBSD 7.1-RELEASE, if you want to be running on a release rather than doing incremental updates along the branch. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0812311021590.41786>