see <a href="http://www.imanlinuxer.blogspot.com">www.imanlinuxer.blogspot.com</a> <div class="gmail_quote">On Jan 7, 2008 9:53 PM, Shawn Powers <<a href="mailto:spowers@inlandlakes.org">spowers@inlandlakes.org </a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">After messing with my NFS server last week to get my thin clients to behave happily, my /home export to the main network, which connects to about 150 OSX machines was set with the "sync" option in /etc/ exports. This seemed to make sense to me, but in practice (ie, today) the performance is so terribly slow that the OSX computers are unusable. After trying to weed out network issues (cheap switches do not make this easy), I tried changing the export to "async" -- and the OSX clients are all behaving magically delicious. The problem, of course, is the threat of "doom and gloom" that goes along with exporting NFS with the async option. I'm curious the ramifications that go along with doing such a thing, and I'm also curious what the "Right Thing" is to do. UPDATE: I just got a call that the computers are not mostly complaining that file locking is working, but if they tell OSX to disable locks, things work again. My suspicion is that I'm looking at quite a !fun day... I realize the clients I'm referring to are not running Linux (those, in fact are working quite nicely), but I'm still interested in anyone's thoughts on the NFS thing... Thanks, -Shawn _______________________________________________ K12OSN mailing list <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/k12osn" target="_blank">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <<a href="http://www.k12os.org" target="_blank"> http://www.k12os.org</a>> </blockquote></div>