diff options
author | Ronnie Sahlberg <ronniesahlberg@gmail.com> | 2009-05-25 12:08:50 +1000 |
---|---|---|
committer | Ronnie Sahlberg <ronniesahlberg@gmail.com> | 2009-05-25 12:08:50 +1000 |
commit | 691379b13df45215c6bc0c05aa1b90de8c506725 (patch) | |
tree | caa4c5e157fea0f7e3f28e81443dc31a57f7eecd /ctdb/web | |
parent | 0891024f7a0923ec6c9c3d14dc4b1c4c07cfa4f8 (diff) | |
download | samba-691379b13df45215c6bc0c05aa1b90de8c506725.tar.gz |
From Flavio Carmo Junior <carmo.flavio@gmail.com>
(with modifications)
Add a webpage about CLAMAV support in CTDB
(This used to be ctdb commit 5fc14f98902ae98abed35eaab3b3495226dcac38)
Diffstat (limited to 'ctdb/web')
-rw-r--r-- | ctdb/web/clamd.html | 78 | ||||
-rw-r--r-- | ctdb/web/documentation.html | 1 |
2 files changed, 79 insertions, 0 deletions
diff --git a/ctdb/web/clamd.html b/ctdb/web/clamd.html new file mode 100644 index 00000000000..4edb4cf23d7 --- /dev/null +++ b/ctdb/web/clamd.html @@ -0,0 +1,78 @@ +<!--#set var="TITLE" value="CTDB and ClamAV Daemon" --> +<!--#include virtual="header.html" --> + +<h1>Setting up ClamAV with CTDB</h1> + +<h2>Prereqs</h2> +Configure CTDB as above and set it up to use public ipaddresses.<br> +Verify that the CTDB cluster works. + +<h2>Configuration</h2> + +Configure clamd on each node on the cluster.<br><br> +For details how to configure clamd check its documentation. + +<h2>/etc/sysconfig/ctdb</h2> + +Add the following lines to the /etc/sysconfig/ctdb configuration file. +<pre> + CTDB_MANAGES_CLAMD=yes + CTDB_CLAMD_SOCKET="/path/to/clamd.sock" +</pre> + +Disable clamd in chkconfig so that it does not start by default. Instead CTDB will start/stop clamd as required. +<pre> + chkconfig clamd off +</pre> + +<h2>Events script</h2> + +The CTDB distribution already comes with an events script for clamd in the file /etc/ctdb/events.d/31.clamd<br><br> +There should not be any need to edit this file. +What you need is to set it as executable, with command like this: +<pre> + chmod +x /etc/ctdb/events.d/31.clamd +</pre> +To check if ctdb monitoring and handling with clamd, you can check outpout of command: +<pre> + ctdb scriptstatus +</pre> + +<h2>Restart your cluster</h2> +Next time your cluster restarts, CTDB will start managing the clamd service.<br><br> +If the cluster is already in production you may not want to restart the entire cluster since this would disrupt services.<br> + +Insted you can just disable/enable the nodes one by one. Once a node becomes enabled again it will start the clamd service.<br><br> + +Follow the procedure below for each node, one node at a time : + +<h3>1 Disable the node</h3> +Use the ctdb command to disable the node : +<pre> + ctdb -n NODE disable +</pre> + +<h3>2 Wait until the cluster has recovered</h3> + +Use the ctdb tool to monitor until the cluster has recovered, i.e. Recovery mode is NORMAL. This should happen within seconds of when you disabled the node. +<pre> + ctdb status +</pre> + +<h3>3 Enable the node again</h3> + +Re-enable the node again which will start the newly configured vsftp service. +<pre> + ctdb -n NODE enable +</pre> + +<h2>See also</h2> + +The CLAMAV section in the ctdbd manpage. + +<pre> + man ctdbd +</pre> + +<!--#include virtual="footer.html" --> + diff --git a/ctdb/web/documentation.html b/ctdb/web/documentation.html index d78a1f0188c..57daf7133e5 100644 --- a/ctdb/web/documentation.html +++ b/ctdb/web/documentation.html @@ -17,6 +17,7 @@ The following documentation should get you started with CTDB. <li><a href="ftp.html">Setting up FTP with CTDB</a> <li><a href="nfs.html">Setting up NFS 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> <li><a href="http://wiki.samba.org/index.php/CTDB_Setup">CTDB Wiki</a> </ul> |