Apparently this bug was fixed in version 1.4.0:
http://www.theether.org/pssh/ChangeLog
Jaunty has 1.4.3, so this should be already fixed there. Now if only we could
get a backport...
--
pssh (parallel-scp) invalid argument
https://bugs.launchpad.net/bugs/29
You received this bug
This is probably a better solution:
--- /usr/bin/parallel-scp 2008-05-07 04:54:39.0 +0300
+++ parallel-scp2009-02-20 13:14:44.0 +0200
@@ -21,7 +21,10 @@
from psshlib.basethread import BaseThread
_DEFAULT_PARALLELISM = 32
-_DEFAULT_TIMEOUT = sys.maxint #
Should I be trying to apply this directly to /usr/bin/parallel-scp? When
I do this I get an error:
brendanmart...@hairball:~$ sudo patch /usr/bin/parallel-ssh psh.diff
patching file /usr/bin/parallel-ssh
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- saving rejects to file
Before applying the patch try to:
$ cd /usr/bin
--
pssh (parallel-scp) invalid argument
https://bugs.launchpad.net/bugs/29
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
The following patch fixes it for me:
--- /usr/bin/parallel-scp 2008-05-07 04:54:39.0 +0300
+++ parallel-scp2009-02-19 17:43:37.0 +0200
@@ -21,7 +21,7 @@
from psshlib.basethread import BaseThread
_DEFAULT_PARALLELISM = 32
-_DEFAULT_TIMEOUT = sys.maxint #
I have also experienced this; when running parallel-scp, or parallel-
rsync I get a bunch of [1] 16:28:58 [FAILURE] server.com (22, 'Invalid
argument'). Parallel-ssh seems to work just fine, I'm using the same
hosts file as for parallel-ssh.
--
pssh (parallel-scp) invalid argument
Confirming this bug as I have the same problem.
** Changed in: pssh (Ubuntu)
Status: New = Confirmed
--
pssh (parallel-scp) invalid argument
https://bugs.launchpad.net/bugs/29
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for so many extra comments I am also using amd64.
--
pssh (parallel-scp) invalid argument
https://bugs.launchpad.net/bugs/29
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list