Date: Tue, 8 Jan 2008 09:23:05 -0800 From: Chuck Swiger <cswiger@mac.com> To: Konrad Heuer <kheuer2@gwdg.de> Cc: freebsd-questions@freebsd.org Subject: Re: OSX NFS-Server && FreeBSD NFS Client Message-ID: <B4BB02A8-CB30-4180-8971-E7F5CAC5F8FF@mac.com> In-Reply-To: <20080108075717.A99137@gwdu60.gwdg.de> References: <20080103073138.G99137@gwdu60.gwdg.de> <872A6988-2C89-4AF1-99E6-57B744C799CB@mac.com> <20080108075717.A99137@gwdu60.gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 7, 2008, at 11:01 PM, Konrad Heuer wrote: >> You really don't want to export a filesystem which itself is being >> mounted remotely. If you want to provide SMB filesharing for these >> files, run Samba on the OS X machine(s) directly. > > Knowing all the drawbacks including reduced bandwith, there are some > important organizational reasons, thus I want to do so. Moreover, > Samba ist just one application on the NFS clients, although an > important one. While I certainly wish you the best of luck, previous experience suggests that the drawbacks to this approach include not functioning properly. NFS is a stateless protocol, except insofar as rpc.lockd in theory provides lockf/flock style locking over the network-- yet Samba/CIFS wants to allow extensive use of client side opportunistic locking, which means that Samba really, really wants to run off of a local filesystem. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B4BB02A8-CB30-4180-8971-E7F5CAC5F8FF>