I've not been able to get scp to work with SourceForge since they upgraded their machines. ssh works fine. Is this related to the protocol mismatch problem that was discussed earlier? My ssh tells me "SSH Version OpenSSH-1.2.2, protocol version 1.5.", and the remote sshd is sending it's version as "Remote protocol version 1.99, remote software version OpenSSH_2.2.0p1". Was there a reasonable way to deal with this? I'm running Linux-Mandrake 7.1 with very little customization or extra stuff. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
[Fred L. Drake, Jr.]
I've not been able to get scp to work with SourceForge since they upgraded their machines. ssh works fine.
Same here. In particular, I can use ssh to log in to shell.sourceforge.net, but attempts to scp there act like this (breaking long lines by hand with \n\t):
And there it sits forever. Several others report the same symptom on SF forums, and assorted unresolved SF Support and Bug reports. We don't know what your symptom is!
Is this related to the protocol mismatch problem that was discussed earlier?
Doubt it. Most commentators pin the blame elsewhere.
... Was there a reasonable way to deal with this?
A new note was added to http://sourceforge.net/support/?func=detailsupport&support_id=110235&group_i d=1 today, including: """ Re: Shell server We're also aware of the number of problems on the shell server with respect to restricitive permissions on some programs - and sourcing of shell environments. We're also aware of the troubles with scp and transferring files. As a work around, we recommend either editing files on the shell server, or scping files to the shell server from external hosts to the shell server, whilst logged in to the shell server. """ So there you go: scp files to the shell server from external hosts to the shell server whilst logged in to the shell server <wink>. Is scp working for *anyone*???
Tim Peters writes:
Exactly the same.
So there you go: scp files to the shell server from external hosts to the shell server whilst logged in to the shell server <wink>.
Yeah, that really helps.... NOT! All I want to be able to do is post a new development version of the documentation. ;-( -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
[Tim]
So there you go: scp files to the shell server from external hosts to the shell server whilst logged in to the shell server <wink>.
[Fred]
Yeah, that really helps.... NOT! All I want to be able to do is post a new development version of the documentation. ;-(
All I want to do is make a measly change to a PEP -- I'm afraid it doesn't ask how trivial your intents are. If some suck^H^H^H^Hdeveloper admits that scp works for them, maybe we can mail them stuff and have *them* copy it over. no-takers-so-far-though-ly y'rs - tim
"TP" == Tim Peters <tim.one@home.com> writes:
TP> So there you go: scp files to the shell server from external TP> hosts to the shell server whilst logged in to the shell server TP> <wink>. Psheesh, /that/ was obvious. Did you even have to ask? TP> Is scp working for *anyone*??? Nope, same thing happens to me; it just hangs. -Barry
[Tim, quoting a bit of immortal SF support prose]
[Barry]
Psheesh, /that/ was obvious. Did you even have to ask?
Actually, isn't this easy to do on Linux? That is, run an ssh server (whatever) on your home machine, log in to the SF shell (which everyone seems able to do), then scp whatever your_home_IP_address:your_home_path from the SF shell? Heck, I can even get that to work on Windows, except I don't know how to set up anything on my end to accept the connection <wink>.
TP> Is scp working for *anyone*???
Nope, same thing happens to me; it just hangs.
That's good to know -- since nobody else mentioned this, Fred probably figured he was unique. not-that-he-isn't-it's-just-that-he's-not-ly y'rs - tim
On Wed, Dec 20, 2000 at 02:52:40PM -0500, Tim Peters wrote:
So there you go: scp files to the shell server from external hosts to the shell server whilst logged in to the shell server <wink>.
Is scp working for *anyone*???
Not for me, anyway. And I'm not just saying that to avoid scp-duty :) And I'm using the same ssh version, which works fine on all other machines. It probably has to do with the funky setup Sourceforge uses. (Try looking at 'df' and 'cat /proc/mounts', and comparing the two -- you'll see what I mean :) That also means I'm not tempted to try and reproduce it, obviously :) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
[Fred L. Drake, Jr.]
I've not been able to get scp to work with SourceForge since they upgraded their machines. ssh works fine.
Same here. In particular, I can use ssh to log in to shell.sourceforge.net, but attempts to scp there act like this (breaking long lines by hand with \n\t):
And there it sits forever. Several others report the same symptom on SF forums, and assorted unresolved SF Support and Bug reports. We don't know what your symptom is!
Is this related to the protocol mismatch problem that was discussed earlier?
Doubt it. Most commentators pin the blame elsewhere.
... Was there a reasonable way to deal with this?
A new note was added to http://sourceforge.net/support/?func=detailsupport&support_id=110235&group_i d=1 today, including: """ Re: Shell server We're also aware of the number of problems on the shell server with respect to restricitive permissions on some programs - and sourcing of shell environments. We're also aware of the troubles with scp and transferring files. As a work around, we recommend either editing files on the shell server, or scping files to the shell server from external hosts to the shell server, whilst logged in to the shell server. """ So there you go: scp files to the shell server from external hosts to the shell server whilst logged in to the shell server <wink>. Is scp working for *anyone*???
Tim Peters writes:
Exactly the same.
So there you go: scp files to the shell server from external hosts to the shell server whilst logged in to the shell server <wink>.
Yeah, that really helps.... NOT! All I want to be able to do is post a new development version of the documentation. ;-( -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
[Tim]
So there you go: scp files to the shell server from external hosts to the shell server whilst logged in to the shell server <wink>.
[Fred]
Yeah, that really helps.... NOT! All I want to be able to do is post a new development version of the documentation. ;-(
All I want to do is make a measly change to a PEP -- I'm afraid it doesn't ask how trivial your intents are. If some suck^H^H^H^Hdeveloper admits that scp works for them, maybe we can mail them stuff and have *them* copy it over. no-takers-so-far-though-ly y'rs - tim
"TP" == Tim Peters <tim.one@home.com> writes:
TP> So there you go: scp files to the shell server from external TP> hosts to the shell server whilst logged in to the shell server TP> <wink>. Psheesh, /that/ was obvious. Did you even have to ask? TP> Is scp working for *anyone*??? Nope, same thing happens to me; it just hangs. -Barry
[Tim, quoting a bit of immortal SF support prose]
[Barry]
Psheesh, /that/ was obvious. Did you even have to ask?
Actually, isn't this easy to do on Linux? That is, run an ssh server (whatever) on your home machine, log in to the SF shell (which everyone seems able to do), then scp whatever your_home_IP_address:your_home_path from the SF shell? Heck, I can even get that to work on Windows, except I don't know how to set up anything on my end to accept the connection <wink>.
TP> Is scp working for *anyone*???
Nope, same thing happens to me; it just hangs.
That's good to know -- since nobody else mentioned this, Fred probably figured he was unique. not-that-he-isn't-it's-just-that-he's-not-ly y'rs - tim
On Wed, Dec 20, 2000 at 02:52:40PM -0500, Tim Peters wrote:
So there you go: scp files to the shell server from external hosts to the shell server whilst logged in to the shell server <wink>.
Is scp working for *anyone*???
Not for me, anyway. And I'm not just saying that to avoid scp-duty :) And I'm using the same ssh version, which works fine on all other machines. It probably has to do with the funky setup Sourceforge uses. (Try looking at 'df' and 'cat /proc/mounts', and comparing the two -- you'll see what I mean :) That also means I'm not tempted to try and reproduce it, obviously :) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
participants (5)
-
barry＠digicool.com -
bckfnn＠worldonline.dk -
Fred L. Drake, Jr. -
Thomas Wouters -
Tim Peters