[Csync2] Feature/change suggestions
Matthias Saou
thias at spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net
Mon Feb 18 13:05:17 CET 2008
Terry Burton wrote :
> On Feb 18, 2008 10:22 AM, Vincent Régnard <vregnard at tbs-internet.com> wrote:
> > Here we have a small group of developpers that plan to code csync2
> > "extra or enhencement patches". We hope to release these patches soon
> > after we have them work well. Star of the job is planned for april this
> > year. We are already thinking at about half a dozen features we would
> > like to develop. If you also have some csync2 features you would need or
> > appreciate, please let us know via this list we read. Any ideas or
> > suggestions are welcome.
>
> Hi,
>
> Bumping this one, "preservation of ownership by matching user/group _string_":
>
> http://lists.linbit.com/pipermail/csync2/2007-December/000322.html
Well, that would indeed be nice. I have a similar "request" : When
doing some testing with csync2 and some big files, I ran into two
issues :
1) It seems that for mode or ownership changes, csync2 re-transfers the
entire file instead of just changing the mode or ownership information.
This is undetectable for small configuration files, but is a severe
performance impact with multi GB files.
2) It seems that all files being transferred are first copied to /tmp
then moved in-place. This is problematic for various reasons when the
final destination is on a different partition :
- If /tmp does not have enough space for the file, things fail.
- Moving the file at the end of the transfer takes more time.
These are two aspects of csync2 which, if "fixed", would make it work
much better in the environments where I use it ;-)
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 8 (Werewolf) - Linux kernel 2.6.23.15-137.fc8
Load : 0.00 0.03 0.05
More information about the Csync2
mailing list