diff options
Diffstat (limited to 'docs/Samba3-HOWTO/TOSHARG-msdfs.xml')
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-msdfs.xml | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/docs/Samba3-HOWTO/TOSHARG-msdfs.xml b/docs/Samba3-HOWTO/TOSHARG-msdfs.xml index f5d066e681..b9dbb84865 100644 --- a/docs/Samba3-HOWTO/TOSHARG-msdfs.xml +++ b/docs/Samba3-HOWTO/TOSHARG-msdfs.xml @@ -23,7 +23,7 @@ <title>Features and Benefits</title> <para> - The Distributed File System (DFS) provides a means of separating the logical + The distributed file system (DFS) provides a means of separating the logical view of files and directories that users see from the actual physical locations of these resources on the network. It allows for higher availability, smoother storage expansion, load balancing, and so on. @@ -40,7 +40,7 @@ A Samba server can be made a DFS server by setting the global Boolean <smbconfoption name="host msdfs"/> parameter in the &smb.conf; file. You designate a share as a DFS - root using the Share Level Boolean <smbconfoption name="msdfs root"/> parameter. A DFS root directory on Samba hosts DFS + root using the share-level Boolean <smbconfoption name="msdfs root"/> parameter. A DFS root directory on Samba hosts DFS links in the form of symbolic links that point to other servers. For example, a symbolic link <filename>junction->msdfs:storage1\share1</filename> in the share directory acts as the DFS junction. When DFS-aware clients attempt to access the junction link, @@ -49,7 +49,7 @@ <para> DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x. - <link linkend="dfscfg">Following sample configuration</link> shows how to setup a DFS tree on a Samba server. + <link linkend="dfscfg">The following sample configuration</link> shows how to setup a DFS tree on a Samba server. In the <filename>/export/dfsroot</filename> directory, you set up your DFS links to other servers on the network. <screen> @@ -62,7 +62,7 @@ </para> <example id="dfscfg"> -<title>smb.conf with DFS configured</title> +<title>smb.conf with DFS Configured</title> <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="netbios name">&example.server.samba;</smbconfoption> @@ -76,14 +76,14 @@ <para>You should set up the permissions and ownership of the directory acting as the DFS root so that only designated - users can create, delete or modify the msdfs links. Also note + users can create, delete, or modify the msdfs links. Also note that symlink names should be all lowercase. This limitation exists to have Samba avoid trying all the case combinations to get at the link name. Finally, set up the symbolic links to point to the network shares you want and start Samba.</para> <para>Users on DFS-aware clients can now browse the DFS tree - on the Samba server at \\samba\dfs. Accessing + on the Samba server at <constant>\\samba\dfs</constant>. Accessing links linka or linkb (which appear as directories to the client) takes users directly to the appropriate shares on the network.</para> </sect1> @@ -93,7 +93,7 @@ <itemizedlist> <listitem><para>Windows clients need to be rebooted if a previously mounted non-DFS share is made a DFS - root or vice versa. A better way is to introduce a + root, or vice versa. A better way is to introduce a new share and make it the DFS root.</para> </listitem> @@ -113,20 +113,20 @@ <para> A network administrator sent advice to the Samba mailing list - after a long sessions trying to determine why DFS was not working. + after long sessions trying to determine why DFS was not working. His advice is worth noting. </para> <para><quote> I spent some time trying to figure out why my particular - dfs root wasn't working. I noted in the documentation that + DFS root wasn't working. I noted in the documentation that the symlink should be in all lowercase. It should be amended that the entire path to the symlink should all be in lowercase as well. </quote></para> <para> - For example, I had a share defined as such: + <quote>For example, I had a share defined as such:</quote> <screen> [pub] @@ -134,8 +134,8 @@ msdfs root = yes </screen> - and I could not make my Windows 9x/Me (with the dfs client installed) - follow this symlink: + <quote>and I could not make my Windows 9x/Me (with the dfs client installed) + follow this symlink:</quote> <screen> damage1 -> msdfs:damage\test-share @@ -143,15 +143,15 @@ </para> <para> - Running a debug level of 10 reveals: + <quote>Running a debug level of 10 reveals:</quote> <programlisting> [2003/08/20 11:40:33, 5] msdfs/msdfs.c:is_msdfs_link(176) is_msdfs_link: /export/home/shares/public_share/* does not exist. </programlisting> - Curious. So I changed the directory name from .../Shares/... to - .../shares/... (along with my service definition) and it worked! + <quote>Curious. So I changed the directory name from <constant>.../Shares/...</constant> to + <constant>.../shares/...</constant> (along with my service definition) and it worked!</quote> </para> </sect2> |