perhaps a simple hack on top of 1.x code base can be to open the
underlying sqlite database of csync2, which can be found generally at
/var/lib/csync2/your.fqdn.name.db, in SQLite Shell and change the existing
prefix to whichever new prefix you want with a simple SQL command.
Regards,
Samba
On
On Thu, Jul 10, 2014 at 01:53:20AM -0400, dlo wrote:
> Lars- I see it's not so far off, but definitely not a drop-in replacement
> (already ran into some problems). It worries me to make so many changes to
> a system that's been working so well for so long... is there really no hope
> for getting
Lars- I see it's not so far off, but definitely not a drop-in replacement
(already ran into some problems). It worries me to make so many changes to
a system that's been working so well for so long... is there really no hope
for getting file-specific syncs working with prefixes in 1.34?
I'm also
Is it definitely a drop-in replacement? (db format is the same, etc.?)
The main csync2 page didn't give me confidence in 2.0, since it has RC next
to it, and I didn't see a changelog. In one of the original messages on
this list about 2.0, you even mention something about inotify and support
for
On Tue, Jul 08, 2014 at 04:31:46AM -0400, dlo wrote:
> I've had csync2 (1.34) working fine for a few years now... it took a bit of
> work to figure out its quirks, but it's been really great and reliable.
> (Thank you, Lars et al!)
Please try 2.0, if you can.
> On one of my machines (rs1), I'm ru
I've had csync2 (1.34) working fine for a few years now... it took a bit of
work to figure out its quirks, but it's been really great and reliable.
(Thank you, Lars et al!)
On one of my machines (rs1), I'm running out of space on the partition
containing the synced folder, so I changed the configu
