o be warned by rsyncrypto in case we decrypt
files "in place", overwriting existing ones ?
maybe rsyncrypto should refuse to overwrite existing files, unless a
--force flag is given ?
I may be able to work on such a patch.
Regards
--
Thomas Constans
Le mercredi 18 juin 2008 à 12:23 +0200, Thomas Constans a écrit :
> Le mercredi 18 juin 2008 à 11:55 +0300, Shachar Shemesh a écrit :
> > Thomas Constans wrote:
> > > And rsyncrypto actually choke on such file, giving a "input/output
> > > error".
> >
Le mercredi 18 juin 2008 à 11:55 +0300, Shachar Shemesh a écrit :
> Thomas Constans wrote:
> > And rsyncrypto actually choke on such file, giving a "input/output
> > error".
> >
> I've uploaded a version with the patch to
> http://www.lingnu.com/downl
Le mardi 17 juin 2008 à 20:01 +0300, Shachar Shemesh a écrit :
> Thomas Constans wrote:
> > I hope it will be ready soon. It is part of a global remote backup
> > service i am setting up.
> >
> >
> So you are competing with me :-)
I think there is enough
Le mardi 17 juin 2008 à 18:36 +0300, Shachar Shemesh a écrit :
> Thomas Constans wrote:
> > Hello,
> >
> > First of all, many thanks for this nice piece of software !
> >
> > I am actually building a pygtk frontend to rsync + rsyncrypto.
> >
> Cool. S
)
myfile.write( os.path.join(root, f )+"\n")
myfile.close()
return filelist
It would be nice if rsyncrypto can handle (meaning ignore) this kind of
file more graciously.
Best regards
Keep up the good work
--
Thom