This email can be read as somewhat self serving. While I cannot deny
that it is, I still think that the reasoning behind it is a valid one to
apply, regardless of the case.
renaud cabrol wrote:
> I'm not a developer so I give back to the open source community by
> donating to the FSF a % of m
>
> I have some little knowledge about C, if it's not too complicated I think
> I could
> handle it.
Sure, but the only problem is that what I have is something for windows,
which I'm not too comfortable with (it was a quick solution with many things
hardcoded etc.)
I can help with a linux versio
Hi,
Shachar, thanks for you long reply and for your effort on rsyncrypto
development.
As I told in a previous email on this list I'm self employed, offering
services to very small business company here in Paris, France. Remote
backup is one thing I try to develop, also at a very small scale.
U
Hi,
I will try tomorrow to upgrade to 1.06 and see if the error is still there.
"I am a bit out of touch with rsyncrypto."
Does it mean that rsyncrypto will not be developed / supported anymore ?
Thanks julian for having a look on it. If upgrading does not solve the
problem I will post more det
No luck in replicating yet. I don't know what causes it.
I am getting a "stat failed" with very long path names, though.
I searched through some old logs and found the error thrown was always (on
windows):
Error removing directory(C:\*filename*): Unknown error
(as opposed to the more verbose "direc
I noticed this on windows too some time back.
If a directory tree, three levels deep, is deleted on the source (after it
would have been encrypted to dest at least once previously), I get this
error.
However, the lowest directory would have been deleted from dest.
Running the exact same command thr
renaud cabrol wrote:
> I would like to know if I'm doing something wrong or if this is a known bug
> and upgrading rsyncrypto is necessary.
>
The bug does not ring a bell, but I am a bit out of touch with rsyncrypto.
> I don't find anything in the bug track.
> rsyncrypto 1.06 is only available
Hello,
I'm using rsyncrypto 0.19-1 on debian etch
It runs through a cron job every night over a 200 GO structure. Here is the
command line :
rsyncrypto -vrc --trim=3 --delete /home/explorations/public/
/home/telesauvegarde/donnees/public/ /home/telesauvegarde/keysdir/public/
/home/telesauvegar
