smb.conf defaults for msdfs parms

[Tim Potter]

On Wed, 2006-02-22 at 16:50 -0600, William Marshall wrote:
> 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

Actually, I'm not sure whether it's a good idea to default the 'msdfs
root' parameter to yes since it is a per-share parameter.  What happens
when every share is the msdfs root?  I can imagine that strange things
could happen.


Tim.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20060227/2425dd0c/attachment.bin