mirror of
https://github.com/samba-team/samba.git
synced 2025-03-03 12:58:35 +03:00
e8e98c9ea0
major changes include: - added NSTATUS type - added automatic mapping between dos and nt error codes - changed all ERROR() calls to ERROR_DOS() and many to ERROR_NT() these calls auto-translate to the client error code system - got rid of the cached error code and the writebmpx code We eventually will need to also: - get rid of BOOL, so we don't lose error info - replace all ERROR_DOS() calls with ERROR_NT() calls but that is too much for one night (This used to be commit 83d9896c1ea8be796192b51a4678c2a3b87f7518)
Setting up MS Dfs in Samba kalele@veritas.com March 2000 Currently, MS Dfs support is a configure time parameter (--with-msdfs). Can be changed later to always compile it in.. To have a server announce itself as a Dfs server, add a "host msdfs=yes" entry to smb.conf. To make a share a Dfs root, add a "msdfs root=yes" entry to the share definition in the smb.conf file. e.g. [pub] path = /export/publicsmb msdfs root = yes To create dfs volumes/junctions in the share, create symbolic links of the format msdfs:server1\share1,server2\share2 and so on. In the above example, create a dfs volume "dfsstorage" in the [pub] share as: cd /export/publicsmb ln -s msdfs:serverA\\share dfsstorage Clicking on dfsstorage from a dfs-aware client will show you the contents of \\serverA\share Shares with "msdfs root = no" (which is the default) entries are served as normal shares and the client stops talking Dfs with Samba after a tconX. NOTES: * Windows clients need to be rebooted if a non-dfs root is made a dfs root or vice versa. A better option is to introduce a new share and make it the dfs root. * Currently there's a restriction that msdfs symlink names should be all lowercase.