Re: error on TTY read: no such file or directory

[lordzork@lordzork.com]

In the gothic chambers of the underworld on Fri 28 Sep 2001 at 13:48 -0400,
Bart Schaefer muttered darkly:

> That's a really strange error.  It's coming from ZLE attempting to read
> one byte from the tty file descriptor, which should have been correctly
> opened long before that point (or else you should have seen a different
> error, earlier).
> 
> Does the same error happen if you log in as someone else and then use
> "su -" to start a root login shell?  Otherwise I'm out of ideas on how
> to tell you to debug it.
> 

the error only happens if i login from a tty. all of the following work
fine:

logging in through ssh
logging in as a different user and suing to root
changing shell to bash and then logging in and typing 'zsh -l'

one clarification: this *is* happening to every user, not just root.
it was just taking longer for the tty error to pop up with the other
users. i've noticed that this amount of time varies; sometimes it's
possible for me to type several commands before it boots me.

one other oddity is that command keys in less don't work properly. for
instance, pressing the down arrow prints '^[[B` instead of scrolling
down; pg down prints '^[[6~'. typing 'q' prints a q; a subsequent enter
will quit. it seems to me that this is somehow related to the tty read
error, since it is apparently affecting the line editor.

not to mention, i have the *exact* zsh setup on three other boxes, and
none of these problems.

for the curious, the login-trace file and related zsh configs can be
found here: http://lzi.n3.net/~zork/zle_error/

t.
 

-- 
4.0k -rw-rw-r--    1 zork     zork       17 Apr 4 17:38 .signature