Re: Segmentation fault
Brought to you by:
thesun
From: <al...@ki...> - 2005-12-09 06:01:37
|
Shachar, Thanks for this.. I love rsync, however the size of my backups now require me to sync my work= to=20 a NAS that is accessed by some really dodgy collegues. I needed an app that= =20 applies encryption and keeps the directory\file structure. rsyncrypto is it= =2E. Both Redhat and Suse did not come with argtable. post my email I discovered a site that had a simple line: "openssl req -x509 -newkey rsa:2048 -keyout key.pem -out req.pem" This meant absolutely nothing to me, but I applied it anyway. then I applied "rsyncrypto -r -c -vv tmp it-nas ./keydir ./req.pem" and the backup worked..BUT not without the error\notice "gzip: unrecognized= =20 option `--rsyncable'" Without this I would have given up on the program. Someone needs to put a simple example on sourceforge or hundred others are= =20 going to experience what I have, and will give in. The userguide on sourceforge is useless: rsyncrypto <plaintext file> <cyphertext file> <key file> <certificate> at the time I thought "what the hell is that ??" Without examples of restoring on the web, I played around with a few comman= ds,=20 trying to understand the logic of the syntax To simulate a recovery I deleted the tmp folder then performed i) rsyncrypto -d -r -c -vv tmp it-nas ./keydir ./req.pem this did nothing ii) rsyncrypto -d -r -c -vv it-nas tmp ./keydir ./req.pem "gzip: stdin: not in gzip format Decrypting tmp/test.jpg error: gunzip failed to run:" I'm using gunzip 1.3.5. Have you any suggestions on: 1) gzip: unrecognized option `--rsyncable'" 2) "gzip: stdin: not in gzip format Decrypting tmp/test.jpg error: gunzip failed to run:" I assume rsyncrypto fully works in debian. =C2=A0I would definately like to= see=20 this app work in Suse. cheers Shannon On Wednesday 07 December 2005 16:50, Shachar Shemesh wrote: > al...@ki... wrote: > >I'm receiving this error on both SuSe9.3 and SuSe10. > > > >The following steps were performed on both: > >1) configure/make/make install argtable-2.4.tar > >2) configure/make/make install rsyncrypto-0.16 > > > >if I type rsyncrypto --help: > >*** glibc detected *** double free or corruption (!prev): 0x08059700 *** > >Aborted > > > > > >if I run rsyncrypto <src> <dst> <key> <master key> ....: > >Segmentation fault > > It's a known bug in argtable, when the error buffer is too small (for > example, because you did not provide four mandatory arguments). If you > apply the attached patch to argtable, the problem is solved. As a side > note, I'll mention that this problem does not affect normal operation. > > I should note that there is a fairly known Israeli joke. One kid did not > talk. The kid was already 4, and not a single word. Not "gogo", nothing. > Then, one morning, during breakfast, he looks up and says "Mom, the hot > chocolate isn't hot enough". The suprised mom is all over the place. She > says to him: "Why didn't you talk until now?", to which he says "So far, > everything was ok". > > I have to say that I was not even aware that Suse, Fedora etc. had the > patched gzip capable of running rsyncrypto. As such, they were not > particularily in my testing focus. For Debian, I'm the argtable package > maintiner, and I made sure that the attached patch went into the > official argtable package. It's great to see that people use rsyncrypto, > and that people use it on platforms different than the ones I though > they would. Maybe I should introduce the occasional proble just so I > hear from people `-). > > Shachar |