smb.conf defaults for msdfs parms
William Marshall
bmarsh at us.ibm.com
Wed Feb 22 22:50:27 GMT 2006
Unless there is a technical reason why, I think the msdfs parameters
should default to yes and then the flexibility of dfs is available when
the admin discovers what he can do.
I realized today how nice the msdfs proxy smb.conf parameter can be to
administrators.
For example, say you have share \\server1\sharea, but \\server1 is getting
full.
If you have all the msdfs parms setup correctly, you can replace the
smb,conf path = information with a msdfs proxy = \server2\sharea and your
windows users will automatically move to the new server.
The problem is the defaults are:
host msdfs = no
msdfs root = no
The reason I want this on by default is if a windows client has connected
to a share that is not msdfs enabled, it will remember that status until
the client reboots, so unless you understood the power of samba here and
you've planned ahead, you can't easily move the share.
Unfortunately, enabling dfs on all shares might not be the same behavior
as windows. Checking the XP client dfs cache info w/ dfsutil shows all my
dfs-enabled samba shares appear in the cache, but not standard windows
shares.
Bill Marshall
More information about the samba-technical
mailing list