[Csync2] changing the certificate

[Christian Wiese]

Hi Art,

first of all thanks for your answer.
I am using csync2 version 1.34 so it's sqlite not sqlite3 I
am using.
It's good to know how I can solve a similar cert. issue in
the future! ;)
What looks a bit more harmful to me is the reported problem
with the actions. Unfortunately I didn't had time to trace
this more, but I tracked it down to the waitpid call which
fails in my test environment (Debian Etch, from source
compiled csync2). Because of the failing waitpid call the
action won't get removed from the db, which would explain
the behavior I described in my mail I reported the issue.

Again, many thanks for your suggestions!

Cheers,
Chris


Tue, 21 Oct 2008 18:25:36 +0200 Art -kwaak- van Breemen
<ard+csync2 at telegraafnet.nl> wrote:

> On Wed, Oct 08, 2008 at 06:53:13PM +0200, Christian Wiese
> wrote:
> > I just started to evaluate csync2, and made a little
> > mistake by overwriting an existing certificate. Is
> > there a way to change/update the certificate for a
> > particular host in the database?
> sqlite3? /var/lib/csync2/*
> sqlite> SELECT peername FROM x509_cert;
> sqlite> DELETE FROM x509_cert where peername=' ... ' ;
> 
> it's sqlite3 or sqlite, depending on which version you
> are using. And remember: when signing the certificates,
> the fields must be empty.
> _______________________________________________
> Csync2 mailing list
> Csync2 at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/csync2