Sami Lehtinen has written me to confirm that this is actually a protocol issue that he is working on. sshd closes the pipe to connections until it has written already received packets, more or less, so scp spinds and waits till it's ready for more data. Hopefully he'll pop on-list and give us an update. :) -- Blue Lang, Unix Voodoo Priest http://www.gator.net/~blue 202 Ashe Ave, Apt 3, Raleigh, NC. 919 835 1540 "A computer is a state machine. Threads are for people who can't program state machines." - Alan Cox, From Larry McVoy's quote page
- Re: scp performance. Bob Babcock
- Re: scp performance. James Treworgy
- Re: scp performance. Daniel Woods
- Re: scp performance. Blue Lang
- Re: scp performance. Atro Tossavainen
- Re: scp performance. Hannes Niemi
- Re: scp performance. P Lanvin
- Re: scp performance. Atro Tossavainen
- Re: scp performance. P Lanvin
- Re: scp performance. E. Chaos Golubitsky
- Re: scp performance. Blue Lang
- Re: scp performance. Blue Lang
- Re: scp performance. David Knight French
- Re: scp performance. owner-ssh
- Re: scp performance. Blue Lang
- Re: scp performance. Sami Lehtinen
- Re: scp performance. Blue Lang
- Re: scp performance. Paul Newhouse
