[Csync2] Do not auto-resolve conflict: This is a removal.
Marc G. Fournier
scrappy at hub.org
Sun Aug 2 18:37:04 CEST 2009
I've got two servers set up right now, with csync2 sync'g various domains
between them ... for now, we have one side hot, one side cold, so only one
side is getting files changed on them, but, periodically, I get
files/directories in the sites cache directory that won't sync on the cold
side:
Deleting
/usr/local/www/domain.com/www/wp-content/cache/supercache/www.domain.com/2005/03/11
on s2.domain.com ...
While syncing file
/usr/local/www/domain.com/www/wp-content/cache/supercache/www.domain.com/2005/03/11:
ERROR from peer s2.domain.com: Directory not empty
Do not auto-resolve conflict: This is a removal.
File stays in dirty state. Try again later...
The thing is, its s1.domain that put those files onto s2 ... so when
s1.domain removed the cache file on its side, why didn't it get removed
from s2 .. and how do I 'force' the removal, without having to manually
log into s2 and do a 'rm <file>'?
I'm running csync2-1.34, and I have conflict resolution set to 'auto
younger' ...
Is there something better I should be doing here?
Thanks ...
----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy at hub.org http://www.hub.org
Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy at hub.org
More information about the Csync2
mailing list