ctdb-web: Remove Samba page

It is now all in the wiki.

Signed-off-by: Martin Schwenke <martin@meltin.net>

diff --git a/web/documentation.html b/web/documentation.html
index 34e15fc86722d93bc2859241830910ca54620987..f4850264ead676a644db643dfd3c49ff5c471b03 100644 (file)
--- a/web/documentation.html
+++ b/web/documentation.html
@@ -33,7 +33,6 @@
 </p>
 
 <ul>
-<li><a href="samba.html">Setting up Samba with CTDB</a>
 <li><a href="ftp.html">Setting up FTP with CTDB</a>
 <li><a href="iscsi.html">Setting up iSCSI with CTDB</a>
 <li><a href="clamd.html">Setting up CLAMD with CTDB</a>

diff --git a/web/samba.html b/web/samba.html
deleted file mode 100644 (file)
index 9e4bf14..0000000
--- a/web/samba.html
+++ /dev/null
@@ -1,97 +0,0 @@
-<!--#set var="TITLE" value="CTDB and Samba" -->
-<!--#include virtual="header.html" -->
-
-<h1>Setting up clustered samba</h1>
-
-It is assumed tou have already installed the ctdb version of samba and also installed, configured and tested CTDB.
-
-<h2>Create a user account</h2>
-
-First you need to initialise the Samba password database so that you have some user that can authenticate to the samba service.<br>
-Do this by running:
-<pre>
-  smbpasswd -a root
-</pre>
-
-Samba with clustering must use the tdbsam or ldap SAM passdb backends, or must be configured to be a member of a domain.<br>
-The rest of the configuration of Samba is exactly as it is done on a normal system.<br><br>
-See the docs on http://samba.org/ for details.
-
-<h2>Critical smb.conf parameters</h2>
-
-A clustered Samba install must set some specific configuration parameters
-<pre>
-  clustering = yes
-  idmap backend = tdb2
-</pre>
-
-<h2>Using smbcontrol</h2>
-
-You can check for connectivity to the smbd daemons on each node using smbcontrol
-<pre>
-  smbcontrol smbd ping
-</pre>
-
-<h2>Using Samba4 smbtorture</h2>
-
-The Samba4 version of smbtorture has several tests that can be used to
-benchmark a CIFS cluster. You can download Samba 4 from Samba website.
-
-The particular tests that are helpful for cluster benchmarking are the RAW-BENCH-OPEN, RAW-BENCH-LOCK and BENCH-NBENCH tests.<br>
-These tests take a unclist that allows you to spread the workload out over more than one node. For example:
-
-<pre>
-  smbtorture //localhost/data -Uuser%password  RAW-BENCH-LOCK --unclist=unclist.txt --num-progs=32 -t60
-</pre>
-
-The file unclist.txt should contain a list of server names in your cluster prefixed by //. For example
-<pre>
- //192.168.1.1
- //192.168.1.2
- //192.168.2.1
- //192.168.2.2
-</pre>
-
-For NBENCH testing you need a client.txt file.<br>
-A suitable file can be found in the dbench distribution at http://samba.org/ftp/tridge/dbench/
-
-
-<h3>CTDB_MANAGES_SAMBA</h3>
-This is a parameter in /etc/sysconfig/ctdb<br><br>
-When this parameter is set to "yes" CTDB will start/stop/restart the local samba daemon as the cluster configuration changes.<br><br>
-When this parameter is set you should also make sure that samba is NOT started by default by the linux system when it boots, e.g.
-<pre>
-  chkconfig smb off
-</pre>
-on a Redhat system and
-<pre>
-  chkconfig smb off
-  chkconfig nmb off
-</pre>
-on a SuSE system.
-
-Example:
-<pre>
-  CTDB_MANAGES_SAMBA="yes"
-</pre>
-
-It is strongly recommended that you set this parameter to "yes" if you intend to use clustered samba.
-
-<h3>CTDB_MANAGES_WINBIND</h3>
-This is a parameter in /etc/sysconfig/ctdb<br><br>
-When this parameter is set to "yes" CTDB will start/stop/restart the local winbind daemon as the cluster configuration changes.<br><br>
-When this parameter is set you should also make sure that winbind is NOT started by default by the linux system when it boots:
-<pre>
-  chkconfig winbind off
-</pre>
-
-Example:
-<pre>
-  CTDB_MANAGES_WINBIND="yes"
-</pre>
-
-It is strongly recommended that you set this parameter to "yes" if you
-intend to use clustered samba in DOMAIN or ADS security mode.
-
-<!--#include virtual="footer.html" -->
-