diff options
| author | John Terpstra <jht@samba.org> | 2005-08-25 16:49:40 +0000 |
|---|---|---|
| committer | Gerald W. Carter <jerry@samba.org> | 2008-04-23 08:47:06 -0500 |
| commit | 6c2e58987bcb3b5fe527f7f6743c549ed6c0c877 (patch) | |
| tree | 700bab687907526be31f9dcadc1e826845562a7b /docs/smbdotconf/misc/remotebrowsesync.xml | |
| parent | cf596ff9a0e5e191cfdc5f219e57844ad35ba7a2 (diff) | |
| download | samba-6c2e58987bcb3b5fe527f7f6743c549ed6c0c877.tar.gz samba-6c2e58987bcb3b5fe527f7f6743c549ed6c0c877.tar.bz2 samba-6c2e58987bcb3b5fe527f7f6743c549ed6c0c877.zip | |
Formatting and other fixes to man pages.
(This used to be commit 411025ed0d6ba37ff00f4afc8ccdc9dae94b62e0)
Diffstat (limited to 'docs/smbdotconf/misc/remotebrowsesync.xml')
| -rw-r--r-- | docs/smbdotconf/misc/remotebrowsesync.xml | 32 |
1 files changed, 20 insertions, 12 deletions
diff --git a/docs/smbdotconf/misc/remotebrowsesync.xml b/docs/smbdotconf/misc/remotebrowsesync.xml index ea25cf48c8..508ec3ab2e 100644 --- a/docs/smbdotconf/misc/remotebrowsesync.xml +++ b/docs/smbdotconf/misc/remotebrowsesync.xml @@ -4,32 +4,40 @@ type="list" xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> <description> - <para>This option allows you to setup <citerefentry><refentrytitle>nmbd</refentrytitle> + <para> + This option allows you to setup <citerefentry><refentrytitle>nmbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry> to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This - is done in a manner that does not work with any non-Samba servers.</para> + is done in a manner that does not work with any non-Samba servers. + </para> - <para>This is useful if you want your Samba server and all local + <para> + This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don't work. The remote workgroup can be anywhere - that you can send IP packets to.</para> + that you can send IP packets to. + </para> - <para>For example:</para> - - <para><command moreinfo="none">remote browse sync = 192.168.2.255 192.168.4.255</command></para> - - <para>the above line would cause <command moreinfo="none">nmbd</command> to request + <para> + For example: +<programlisting> +<command moreinfo="none">remote browse sync = 192.168.2.255 192.168.4.255</command> +</programlisting> + the above line would cause <command moreinfo="none">nmbd</command> to request the master browser on the specified subnets or addresses to - synchronize their browse lists with the local server.</para> + synchronize their browse lists with the local server. + </para> - <para>The IP addresses you choose would normally be the broadcast + <para> + The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it - is in fact the browse master on its segment.</para> + is in fact the browse master on its segment. + </para> </description> <value type="default"></value> |