Date: Thu, 07 Jul 2011 11:06:20 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: rmacklem@uoguelph.ca Cc: rc@FreeBSD.org Subject: Re: nfsd script update review Message-ID: <20110707.110620.989156660090715808.hrs@allbsd.org> In-Reply-To: <347974293.291780.1310001747423.JavaMail.root@erie.cs.uoguelph.ca> References: <347974293.291780.1310001747423.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Rick Macklem <rmacklem@uoguelph.ca> wrote in <347974293.291780.1310001747423.JavaMail.root@erie.cs.uoguelph.ca>: rm> Hi, rm> rm> Someone just pointed out that a -current system won't work rm> when the old nfs server isn't available. rm> rm> That reminded me about the /etc/rc.d/nfsd script update rm> which needs a review. It's at: rm> http://people.freebsd.org/~rmacklem/rc.conf rm> (There is both a diff and the updated script there.) rm> rm> This nfsd change allows the script /etc/rc.d/nfsserver rm> to be deleted. Looks good to me. By the way, one thing I noticed when I tested the new NFS implementation (mainly for the version 3) was that NFS file handle seemed not compatible with the old one. The reason why I thought so was that when I went back and forth between the two implementations on an file server, I had to do remount on all of the clients due to "Stale NFS file handle" error. I am sorry for my laziness not investigating the changes, but is my understanding correct? If true, this will be an obstacle when one wants to seamlessly upgrade his NFS server with a lot of clients. I want to know if there is any workaround for that. -- Hiroki [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAk4VFJwACgkQTyzT2CeTzy3ZowCgilztEYLIaxhLuOBdbqNPeCdW qQMAoIp0VQ3guZfklX6Br0jQVBZPICxg =rOLS -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110707.110620.989156660090715808.hrs>