Geert Stappers wrote:
Op 29-12-2007 om 13:30 schreef Del Merritt:
Rick Thomas wrote:
Also, make sure your ssh-client machine doesn't go to sleep while
waiting...
Thanks. I'm trying this out at the moment. Then again, I'm also "here"
and the install is 96% complete, so I may actually be around when it
finishes, mooting the issue (for me).
With a carbon copy, Cc:, to [EMAIL PROTECTED],
is the bugreport kept up-to-date.
Cheers
Geert Stappers
P.S.
Please tell when the install finishes,
preferable to the address of the bugreport.
Adding "ServerAliveInterval 2" to my .ssh/config file allows me to
complete the install without further issues. I now have a Linksys
"slug" running debian. Huzzah and all that. A "minimal" fix to this
would be to document the issue in a way that reminds users to modify
their .ssh/config file in this manner if their site's security policy
allows it. If it is not permitted for some reason, then if there is a
way that the ssh server on the in-progress system can do this keep
alive, it might result in fewer surprises and less end-user frustration.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
