cannot parse for more than one -O/-o options; cannot use -i option
GoogleCodeExporter opened this issue · 5 comments
GoogleCodeExporter commented
This is a forwarded bug report from Debian, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533416 and if possible
include 533416-forwarded@bugs.debian.org in any correspondence.
Problem description:
parallel-scp and parallel-ssh are not able to accept
1./ more than one -O options and translate them to -o options of the
corresponding applications.
2./ -i (identity) option.
A patch (for parallel-scp) is attached, which solves the issue, though not all
possible combination of the optional arguments are implemented and/or tested. A
similar workaround is available for the parallel-ssh. Maybe, the argument
parsing of the parallel-scp/ssh needs some reconsiderations...
Introducing the use of ':' in the folder description can assign file transfer
direction. Of course from remote->local direction the source files shall have
different names to avoid overwriting them.
As a wish this could be avoided by the use of hostname folders for the local
target...
(This bug was reported
https://bugs.launchpad.net/ubuntu/+source/pssh/+bug/387816)
Original issue reported on code.google.com by and...@pollock.id.au on 12 May 2014 at 12:15
hpreusse commented
As mentioned, the has reported to Ubuntu too. Attached to that issue is a patch, which is told sove the issue. Kindly have a look at it. Thanks!
lilydjwg commented
Um, where is the patch? Could you provide a link?
hpreusse commented
If you open the link "https://bugs.launchpad.net/ubuntu/+source/pssh/+bug/387816", you'll see attachment in the posts from "Steger Jozsef (steger)"
lilydjwg commented
That patch no longer applies. Could you come up with an updated one?
hpreusse commented
I'm not the author of the patch and I don't speak python. Sorry!
- I checked if double -O option is accepted. This seems to work, but I can't check if they are effective.
- the option -i is definitely not present.
I may ask the original author of the patches, but I'm not sure if I get an answer 12 years after submitting a patch.