search for: ilsfx

Displaying 5 results from an estimated 5 matches for "ilsfx".

Did you mean: ilsf
2015 Aug 17
7
Error with paths with ()'s
...or 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 fine. P...
2015 Aug 17
0
Error with paths with ()'s
...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...
2015 Aug 17
0
Error with paths with ()'s
...efore. 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...
2014 Aug 30
1
Cleanest way to find out if it was a --dry-run
...[62154] total size is 327,680,000 speedup is 68,739.25 (DRY RUN) but I don't think you can output stats at the receiver-side, and I don't think there's any other mention of the dry run in the receiver-side log. In my pre-xfer script, I see this: RSYNC_ARG1=--server RSYNC_ARG2=-nltrRze.iLsfx RSYNC_ARG3=--log-format=X RSYNC_ARG4=--bwlimit=256 RSYNC_ARG5=--delete-during RSYNC_ARG6=--delete-excluded RSYNC_ARG7=--force RSYNC_ARG8=--partial-dir RSYNC_ARG9=/in-progress/partial RSYNC_ARG10=--link-dest RSYNC_ARG11=/latest/data RSYNC_ARG12=--info=STATS2 RSYNC_ARG13=--debug=EXIT RSYNC_ARG14=. RS...
2016 May 04
2
[Bug 11893] New: rsync should check local file access permission before connecting to remote end
https://bugzilla.samba.org/show_bug.cgi?id=11893 Bug ID: 11893 Summary: rsync should check local file access permission before connecting to remote end Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core