On Mon, Aug 06, 2007 at 03:03:09PM -0700, Ray Van Dolson wrote:
In any case, setting strict locking = no on my Samba server makes
things work, so this at least is getting me by.
posix locking = no is more appropriate here.
But however: DONT re-export nfs-imported shares with Samba.
Install
But however: DONT re-export nfs-imported shares with Samba.
Install Samba on the NFS server.
Just wondering as I have seen this advice a few times in the past.
Would it be possible to use msdfs to make it look to the users that the
files are still on one server as I have been exporting NFS
On Tue, Aug 07, 2007 at 04:56:10AM -0400, John Drescher wrote:
But however: DONT re-export nfs-imported shares with Samba.
Install Samba on the NFS server.
Just wondering as I have seen this advice a few times in the past.
Would it be possible to use msdfs to make it look to the
Sure, but to switch from non-dfs to dfs be aware that you
have to boot all clients. It may also be possible that
you're right now sitting on a version that has the msdfs
options set to yes. Check your testparm output.
Thanks, I know I have it set to no. Are there any serious drawbacks of
I have a situation involving Samba that I _believe_ may be the fault of
a buggy or old NFS daemon, but am not sure. I'm hoping someone can
explain to me what is going on here (I have found a workaround).
I have a Samba server on Fedora 7 (3.0.25b + whatever patches Fedora
includes). This server
