Tony Holmes wrote:
> > It seems that your shell profile executes stty(1) even
> > for non-interactive shells. That is wrong. Make sure
> > that you shell profiles and rc files do not call stty
> > or produce any output for non-interactive sessions.
> > Such output confuses scp.
>
> So obv
Tony Holmes wrote:
> I have jails and dedicated servers set up with various FreeBSD flavours
> (4.11, 6.2, 7) on i386 and amd64.
>
> Some systems I have no problems with scp/sftping to. Others I get this:
>
> [EMAIL PROTECTED] ~
> 7:49am > scp foo.tar.gz [EMAIL PROTECTED]:~/
> Password:
> It seems that your shell profile executes stty(1) even
> for non-interactive shells. That is wrong. Make sure
> that you shell profiles and rc files do not call stty
> or produce any output for non-interactive sessions.
> Such output confuses scp.
So obvious!
The offender:
.login
stty erase
Ok, I'm having a n00b moment here.
I have jails and dedicated servers set up with various FreeBSD flavours
(4.11, 6.2, 7) on i386 and amd64.
Some systems I have no problems with scp/sftping to. Others I get this:
[EMAIL PROTECTED] ~
7:49am > scp foo.tar.gz [EMAIL PROTECTED]:~/
Password:
stty: