This is a discussion on Programs run over ssh aren't getting real ttys. within the OpenSSH Development forums, part of the Networking and Network Related category; I use OpenSSH on a number of machines. If I connect to most of my machines and open a bash ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I use OpenSSH on a number of machines. If I connect to most of my
machines and open a bash shell the first three file descriptors of bash are something like /dev/pts/6. On these machines OpenSSH is as good as a "real" terminal. However, I am putting together an embedded system and I must minimize the size of the installed system. I have OpenSSH working on this system but, when I connect and run bash the first three file descriptors are something like socket: [460]. The issue on this system is a number of tty related functions fail, greatly impairing my ability to use all but the simplest terminal programs. What is wrong? What must I do to enable programs run over ssh (such as bash) to get real pseudo-ttys and not simple sockets? Thank you for your time, James Steven Supancic III _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@mindrot.org https://lists.mindrot.org/mailman/li...enssh-unix-dev |