Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

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

lordzork@xxxxxxxxxxxx wrote:

open("/tmp/login-trace", O_WRONLY|O_CREAT|O_TRUNC|O_NOCTTY|O_LARGEFILE, 0666) = 3
fcntl64(2, F_DUPFD, 10)                 = 13
close(2)                                = 0
dup2(3, 2)                              = 2
ioctl(2, SNDCTL_TMR_TIMEBASE, 0xbffff8d8) = -1 ENOTTY (Inappropriate ioctl for device)

fd 2 does not look like tty, does it? I presume you do exec > /tmp/login-trace very early in your /etc/zshenv

You noticed it, dd not you? Have you checked your zshenv for stderr redrection? (it was to be exec 2> /tmp/login-trace, of course).

Still there is something weird going on:

write(10, "\r\33[m\33[m\33[m\33[J\n\33[1;30m[ \33[1;37mlc"..., 270) = 270
write(10, "\33[K", 3)                   = 3
read(10, "l", 1)                        = 1
write(10, "l", 1)                       = 1
read(10, "s", 1)                        = 1
write(10, "\10ls", 3)                   = 3
read(10, "syJ\10\10\0\0\0\0\0\0\0\0\240G\f\10\0\0\0\0\1\0\0\0\0\0"..., 1) = 1025

Oops. Where does this last line comes from?

that is  probably where it booted me. i typed ls once and it ran, then
again and it froze after the first 'l'.

It was not my question. I do not understand where this data comes from and how can read one byte return 1025 bytes. It looks more like a contents of readdir() but I have no idea how can it appear on shell input.


PS please keep further conversation on the list.

Messages sorted by: Reverse Date, Date, Thread, Author