Hello, Fabrice. I looked into this a little bit, trying different commands, but could not get anything to work. When I use 'plink' instead of 'plink-ssh', at least the error message changes (and it seems better):
$ rsync --debug=all --msgs2stderr --rsh 'plink' -av testdir david@testserver: opening connection using: plink -l david testserver rsync --server -vlogDtpre.iLsfxC --debug=ALL . . (10 args) Unable to read from standard input: The parameter is incorrect. rsync: safe_read failed to read 4 bytes [sender]: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(276) [sender=3.1.2] [sender] _exit_cleanup(code=12, file=io.c, line=276): about to call exit(12) That second error message looks better because it seems like rsync is actually exchanging data with plink. To debug this further, you might want to build a debug version of rsync that logs all messages sent and received. --David On Wed, Jan 24, 2018 at 11:27 AM, Fabrice Popineau <fabrice.popin...@gmail.com> wrote: > Hi, > > Quick question : is there a way to make rsync use pageant to unlock keys? > Something seems flawed with rsync. > > I have pageant running and keys loaded. > > I can : > > $ plink-ssh -l semantic foundry2.supelec.fr ls -al > total 44 > drwxr-xr-x 3 semantic semantic 4096 Sep 12 2016 . > drwxr-xr-x 6 root root 4096 Aug 24 2015 .. > -rw------- 1 semantic semantic 2944 Jan 15 23:58 .bash_history > -rw-r--r-- 1 semantic semantic 220 Aug 24 2015 .bash_logout > ... > $ > > plink-ssh is using pageant as expected without requesting to type a password > to unlock keys. > > But I can't use plink-ssh in rsync: > > $ rsync --debug=ALL -a -e 'plink-ssh -agent -batch' /c/Home/Org/ > seman...@host.mydomain.fr:/home/semantic/popineau/ > opening connection using: plink-ssh -agent -batch -l semantic > host.mydomain.fr rsync --server -logDtpre.iLsfxC --debug=ALL . > /home/semantic/popineau/ (12 args) > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(226) > [sender=3.1.2] > [sender] _exit_cleanup(code=12, file=io.c, line=226): about to call exit(12) > > > I have not been able to circumvent this problem. I tried many ways, > including using cygnative, but with no result. > > I suspect a problem in rsync or its MSYS2 port but I may have overlooked > something. > Anybody can comment on this issue? > > Best regards, > > Fabrice > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Msys2-users mailing list > Msys2-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/msys2-users > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
