From 39539a2d1784f04245ed7abc84c4f39e1601afa4 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Mon, 25 May 2009 11:44:27 +1000 Subject: [PATCH] document the new support for ClamAV --- doc/ctdbd.1 | 45 ++++++++++++++++++++++++++++++++++++-- doc/ctdbd.1.html | 37 ++++++++++++++++++++++++++++++-- doc/ctdbd.1.xml | 56 ++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 134 insertions(+), 4 deletions(-) diff --git a/doc/ctdbd.1 b/doc/ctdbd.1 index d6ac7ba1..33424476 100644 --- a/doc/ctdbd.1 +++ b/doc/ctdbd.1 @@ -1,11 +1,11 @@ .\" Title: ctdbd .\" Author: .\" Generator: DocBook XSL Stylesheets v1.73.2 -.\" Date: 05/14/2009 +.\" Date: 05/25/2009 .\" Manual: .\" Source: .\" -.TH "CTDBD" "1" "05/14/2009" "" "" +.TH "CTDBD" "1" "05/25/2009" "" "" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -508,6 +508,47 @@ The NAT\-GW node is assigned the CTDB_NATGW_PUBLIC_IP to the designated interfac All other nodes in the group are configured with a default route of metric 10 pointing to the designated NAT GW node\. .PP This is implemented in the 11\.natgw eventscript\. Please see the eventscript for further information\. +.SH "CLAMAV DAEMON" +.PP +CTDB has support to manage the popular anti\-virus daemon ClamAV\. This support is implemented through the eventscript : /etc/ctdb/events\.d/31\.clamd\. +.SS "Configuration" +.PP +Start by configuring CLAMAV normally and test that it works\. Once this is done, copy the configuration files over to all the nodes so that all nodes share identical CLAMAV configurations\. Once this is done you can proceed with the intructions below to activate CTDB support for CLAMAV\. +.PP +First, to activate CLAMAV support in CTDB, edit /etc/sysconfig/ctdb and add the two lines : +.sp +.RS 4 +.nf +CTDB_MANAGES_CLAMD=yes +CTDB_CLAMD_SOCKET="/path/to/clamd\.socket" +.fi +.RE +.PP +Second, activate the eventscript by making it executable: +.sp +.RS 4 +.nf +chmod +x /etc/ctdb/events\.d/31\.clamd +.fi +.RE +.PP +Third, CTDB will now be starting and stopping this service accordingly, so make sure that the system is not configured to start/stop this service automatically\. On RedHat systems you can disable the system starting/stopping CLAMAV automatically by running : +.sp +.RS 4 +.nf +chkconfig clamd off +.fi +.RE +.PP +Once you have restarted CTDBD, use +.sp +.RS 4 +.nf +ctdb scriptstatus +.fi +.RE +.sp +and verify that the 31\.clamd eventscript is listed and that it was executed successfully\. .SH "SEE ALSO" .PP ctdb(1), onnode(1) diff --git a/doc/ctdbd.1.html b/doc/ctdbd.1.html index 7ac33c7d..e63c36fa 100644 --- a/doc/ctdbd.1.html +++ b/doc/ctdbd.1.html @@ -531,10 +531,43 @@ CTDB_CAPABILITY_RECMASTER=no

This is implemented in the 11.natgw eventscript. Please see the eventscript for further information. -

SEE ALSO

+

ClamAV Daemon

+CTDB has support to manage the popular anti-virus daemon ClamAV. +This support is implemented through the +eventscript : /etc/ctdb/events.d/31.clamd. +

Configuration

+Start by configuring CLAMAV normally and test that it works. Once this is +done, copy the configuration files over to all the nodes so that all nodes +share identical CLAMAV configurations. +Once this is done you can proceed with the intructions below to activate +CTDB support for CLAMAV. +

+First, to activate CLAMAV support in CTDB, edit /etc/sysconfig/ctdb and add the two lines : +

+CTDB_MANAGES_CLAMD=yes
+CTDB_CLAMD_SOCKET="/path/to/clamd.socket"
+

+Second, activate the eventscript by making it executable: +

+chmod +x /etc/ctdb/events.d/31.clamd
+

+Third, CTDB will now be starting and stopping this service accordingly, +so make sure that the system is not configured to start/stop this service +automatically. +On RedHat systems you can disable the system starting/stopping CLAMAV automatically by running : +

+chkconfig clamd off
+

+

+Once you have restarted CTDBD, use +

+ctdb scriptstatus
+

+and verify that the 31.clamd eventscript is listed and that it was executed successfully. +

SEE ALSO

ctdb(1), onnode(1) http://ctdb.samba.org/ -

COPYRIGHT/LICENSE


+

COPYRIGHT/LICENSE


Copyright (C) Andrew Tridgell 2007
Copyright (C) Ronnie sahlberg 2007

diff --git a/doc/ctdbd.1.xml b/doc/ctdbd.1.xml index 555ca06d..7d94e87a 100644 --- a/doc/ctdbd.1.xml +++ b/doc/ctdbd.1.xml @@ -948,6 +948,62 @@ CTDB_CAPABILITY_RECMASTER=no +ClamAV Daemon + +CTDB has support to manage the popular anti-virus daemon ClamAV. +This support is implemented through the +eventscript : /etc/ctdb/events.d/31.clamd. + + +Configuration + +Start by configuring CLAMAV normally and test that it works. Once this is +done, copy the configuration files over to all the nodes so that all nodes +share identical CLAMAV configurations. +Once this is done you can proceed with the intructions below to activate +CTDB support for CLAMAV. + + + +First, to activate CLAMAV support in CTDB, edit /etc/sysconfig/ctdb and add the two lines : + + +CTDB_MANAGES_CLAMD=yes +CTDB_CLAMD_SOCKET="/path/to/clamd.socket" + + + +Second, activate the eventscript by making it executable: + + +chmod +x /etc/ctdb/events.d/31.clamd + + + +Third, CTDB will now be starting and stopping this service accordingly, +so make sure that the system is not configured to start/stop this service +automatically. +On RedHat systems you can disable the system starting/stopping CLAMAV automatically by running : + +chkconfig clamd off + + + + + +Once you have restarted CTDBD, use + +ctdb scriptstatus + +and verify that the 31.clamd eventscript is listed and that it was executed successfully. + + + + + + + + SEE ALSO ctdb(1), onnode(1) -- 2.34.1