Displaying 6 results from an estimated 6 matches for "logdtpre".
2013 Apr 02
1
RFC: More explicit ssh agent forwarding on SSH_ASKPASS confirmation
...ey requires confirmation,
the is quite terse: "Allow use of key foobar?
Key fingerprint abcdf."
It would be desirable to have instead a text like:
Confirmation is required before allowing usage of key foobar
Key fingerprint abcdf.
to process 1234 (ssh example.com rsync --server --sender -logDtpre.iLsf)
allegedly
for "connecting to example.com (1.2.3.4)"
The rsync command line would be recovered by the agent itself, thus
being quite trustworthy.
In this case the example represented a local application.
If it was a forwarded request it could be:
Confirmation is required before al...
2015 Aug 17
7
Error with paths with ()'s
...ss an error I haven’t seen before. Normally I do this sync via a mounted file system, but this time I tried to do it over ssh:
find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{} \;
bash: -c: line 0: syntax error near unexpected token `('
bash: -c: line 0: `rsync --server -logDtpre.iLsfx --log-format=X --partial . /Volumes/Drive5/./Taxes (2012)/W2 (2012).pdf'
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.1]
If I mount Drive5 and run the same command, it works fi...
2015 Aug 17
0
Error with paths with ()'s
...Normally I do
> this sync via a mounted file system, but this time I tried to do it
> over ssh:
>
> find . -type f -atime -1 -exec rsync -aP {}
> 10.0.0.11:/Volumes/Drive5/{} \; bash: -c: line 0: syntax error near
> unexpected token `(' bash: -c: line 0: `rsync --server
> -logDtpre.iLsfx --log-format=X --partial . /Volumes/Drive5/./Taxes
> (2012)/W2 (2012).pdf' 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.1]
>
> If I mount Drive5 and run the...
2015 Aug 17
0
Error with paths with ()'s
...’t seen before. Normally I do this sync via a mounted file system, but this time I tried to do it over ssh:
>
> find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{} \;
> bash: -c: line 0: syntax error near unexpected token `('
> bash: -c: line 0: `rsync --server -logDtpre.iLsfx --log-format=X --partial . /Volumes/Drive5/./Taxes (2012)/W2 (2012).pdf'
> 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.1]
>
> If I mount Drive5 and run the same c...
2009 Jan 07
1
DO NOT REPLY [Bug 6020] New: support/rrsync fails when server-side options include "-e."
...c error: unexplained error (code 255) at io.c(632) [sender=3.0.4]
This does not appear to happen when the 'e' follows other characters on the
server side. For example, "rsync -a file rem:." on the client side results in
arguments that look like this on the server: "--server -logDtpre.iLs . .".
In this case, everything is fine. On the other hand, if you try
"rsync file rem:." on the client side, the arguments on the server look
like this: "--server -e.Ls . .", and it fails.
I believe the problem is on line 147 of support/rrsync. If I change it from...
2004 May 03
1
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
Rsync Issue Solaris8
When performing a simple rsync between servers I was getting the
following error:
root:#> rsync -e ssh -va /export/home/a078479/bob
smmk39:/export/home/a078479/
ksh: rsync: not found
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
root:#>
I was thorghrough in setting up rsync to be