[Csync2] csync2 config file question
Clifford Wolf
clifford at clifford.at
Thu Apr 6 14:38:17 CEST 2006
Hi,
On Wed, Apr 05, 2006 at 10:31:17PM -0700, Eric Liang wrote:
> we have a dynamic environment, with a groups change all the time.
> new project launch, add machines to a vip, etc.
> So after I change the conf file, do I need to stop the csync2 process
> and rerun it?
I assume with 'csync2 process' you mean the daemon (csync2 -ii).
The daemon re-reads to config file automatically for each connection. So no
need to restart it.
Don't forget that some configuration changes also require additional
measures (such as running 'csync2 -TI'). See manual section '5.5
Bootstrapping large setups' for details.
> also can I include the /etc/csync2.cfg in the list for sync?
yes. In fact I'm using csync2 with such a setup on many of my clusters. But
you should be aware of the security implications:
if one becomes root on one of the machines he can change the csync2
configuration for all the other machines and so gain warite access to every
file on every host in the cluster. So you should only sync the csync2.cfg
file when this is not an issue (e.g. because the cluster host are so
identical that if one is able to become root on one host he is also able
the become root on the others without csync2).
> Also, how robust if I do a csync2 -ii &?
I'd recommend running the csync2 daemon using inetd. The primary use for
the 'csync2 -ii' mode is debugging csync2..
yours,
- clifford
--
SSSS PPPP L The SPL Programming Language
S P P L http://www.clifford.at/spl/
SSSS PPPP L ----------------------------------------------------
S P L An object oriented, stateful, simple, small, c-like,
SSSS P LLLL embeddable, feature rich, dynamic scripting language
"C is quirky, flawed, and an enormous success." - Dennis M. Ritchie.
More information about the Csync2
mailing list