Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Y test failures (zpty)
- X-seq: zsh-workers 16817
- From: Clint Adams <clint@xxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxx>
- Subject: Re: Y test failures (zpty)
- Date: Tue, 12 Mar 2002 13:17:13 -0500
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <15501.49040.499816.469598@xxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20020311053241.GA9027@xxxxxxxx> <1020311182942.ZM27214@xxxxxxxxxxxxxxxxxxxxxxx> <20020311190231.GA21327@xxxxxxxx> <1020311192523.ZM27256@xxxxxxxxxxxxxxxxxxxxxxx> <15501.49040.499816.469598@xxxxxxxxxxxxxxxxxx>
> I once had a similar problem on that Digital Unix box. It turned out
> that for some reason a /dev/ptyXX was free but the corresponding
> /dev/ttyXX was not writable by anyone else than root. That made
> get_pty() fail, of course.
>
> Maybe we should change that function to re-try /dev/pty's in that
> case? Haven't seen that problem anywhere else, though.
I don't know about Digital Unix, but looking at the sources for
OpenSSH, modemu, and rxvt-ml, I see that OSF/1 has something called
openpty().
Also, there is grantpt() and unlockpt(), getpty(), /dev/ptmx, /dev/ptc
(AIX), /dev/ptym/clone, and various sets of static /dev/pty.+ device
nodes.
All three programs mentioned above use build-time decisions, so I am
confused as to how binaries are portable between systems that do and do
not support Unix98 pty's.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author