[Csync2] Syntax error on lock-timeout

Francisco Reyes lists at natserv.net
Mon May 27 18:03:20 CEST 2013


On 05/27/2013 04:13 AM, Lars Ellenberg wrote:
> The "lock-timeout" parameter is in the 2.x sources only.

Ok. Thanks for the info.

> to be able to use not only sqlite, but also mysql or pgsql as backend.

What would be the advantage of using Postgres as backend? Faster?
Handle larget setups? Is there documentation in the RC2 on how to 
connect to Postgresql?


>>> I saw it is in RC2. Is it stable yet for production?
>
> I sure hope so.

ETA for gold?

> Note that I put that "lock-timeout" patch in there in 2009,
> so if you feel more comfortable with going with "the latest before
> all the changes", rather with current git:

I was just trying whatever version was available with Ubuntu repository 
and later was going to do the same with FreeBSD, but may go with RC2 
instead.

> I've never run into this problem myself, but then we usually don't use
> it in a way that operates on millions of files at once...

I really would like to understand why the lock even happened.
Is it basically telling me there is another instance running?

Since I am running this manually and would wait for it to finish before 
trying the next how was there even a lock issue?

In this particular test I was doing my VMware desktop directory so it 
was "only" 28K files, but many of the files are hundreds of MBs. Trying 
to test csync2 as much as I can on my home setup before trying tens of 
millions.


More information about the Csync2 mailing list