Ah, figured it out, the go ssh terminal doesn't support allocating a
pty (so no concept of screen size, raw vs cooked etc), by default
openssh will request a pty _unless_ you pass a command, ie
ssh someone@somewhere /bin/ls
Won't allocate a pty, you can check this by doing ssh somewhere top,
top will whinge because there isn't proper terminal control.
However, when there is no command supplies, ssh requests a shell
session, and a pty, this is what is failing. You can disable the
automatic pty setting with -T, or in .ssh/config, or a bunch of other
ways
% ssh foo@localhost -T -p 2022
foo@localhost's password:
> hello
hello
On Tue, Dec 2, 2014 at 1:48 PM, Dave Cheney <
da...@cheney.net> wrote:
> Os, my mistake, I thoght you were using the client against sshd. I'm not sure if or where the os would log an issue if a process couldn't allocate a new tty. Ada guess, have you run out of file descriptors?
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/golang-nuts/rIWZIjsXoqg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
golang-nuts...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.