zsh-workers
 help / color / mirror / code / Atom feed
From: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk, lordzork@lordzork.com
Subject: Re: error on TTY read: no such file or directory
Date: Sun, 30 Sep 2001 20:40:19 +0400	[thread overview]
Message-ID: <3BB74AF3.8000600@mow.siemens.ru> (raw)
In-Reply-To: <1010930162212.ZM21385@candle.brasslantern.com>

Bart Schaefer wrote:

> On Sep 30,  1:38pm, Zefram wrote:
> } Subject: Re: error on TTY read: no such file or directory
> }
> } lordzork@lordzork.com wrote:
> } >i made a new strace, this time without zsh reading any of its start up
> } >files. my idea was that this would make it easier to read, but the new
> } >strace looks completely different from the old one, at least to me.
> } 
> } It's still doing the same impossible thing.
> 
> I never saw the previous trace.   Looking at this one, I note that it's
> doing this impossible thing a lot, but only on fd 10, and sometimes zsh
> just ignores the problem and loops.  (That would happen when errno == 0,
> or if the impossible occurred somewhere other than in getkey().)
> 


In first strace I got it does it exactly once and then bails out. Not 
that it helps much.


> Ignoring the problem would mean that zsh discarded at least one char of
> input if there really were any, but there's no evidence of input being
> lost.  That in turn makes me think that reads from the tty are behaving
> as if they're non-blocking, but for some reason are returning 1025 when
> they should be returning -1 with EWOULDBLOCK.
> 


I very much like to see what happens with "standard" mingetty instead of 
agetty. There is always a small chance it sets tty into some weird mode.


-andrej


      reply	other threads:[~2001-09-30 16:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010910200737.A6256@hithaeglir.net>
     [not found] ` <001f01c13abb$6997dca0$21c9ca95@mow.siemens.ru>
     [not found]   ` <20010911084904.A11501@hithaeglir.net>
     [not found]     ` <1010911140155.ZM24429@candle.brasslantern.com>
     [not found]       ` <20010928121347.B16561@hithaeglir.net>
     [not found]         ` <3BB56D03.2000300@mow.siemens.ru>
     [not found]           ` <20010929034953.E16561@hithaeglir.net>
     [not found]             ` <3BB62E93.10802@mow.siemens.ru>
     [not found]               ` <20010929170811.G16561@hithaeglir.net>
2001-09-29 21:28                 ` Borsenkow Andrej
     [not found]                   ` <20010929173848.H16561@hithaeglir.net>
2001-09-29 21:56                     ` Borsenkow Andrej
2001-09-29 22:11                       ` lordzork
2001-09-29 22:19                         ` Borsenkow Andrej
2001-09-29 22:31                           ` lordzork
2001-09-29 22:39                         ` Bart Schaefer
2001-09-30  0:24                           ` lordzork
2001-09-30  1:20                             ` Zefram
2001-09-30  2:23                               ` Bart Schaefer
2001-10-01  9:31                                 ` Peter Stephenson
2001-09-30  1:24                             ` Bart Schaefer
2001-09-30  1:34                               ` lordzork
2001-09-30  6:25                                 ` Borsenkow Andrej
2001-09-30 11:23                                   ` lordzork
2001-09-30 11:48                                   ` lordzork
2001-09-30 12:38                                     ` Zefram
2001-09-30 15:44                                       ` Borsenkow Andrej
2001-09-30 16:22                                       ` Bart Schaefer
2001-09-30 16:40                                         ` Borsenkow Andrej [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BB74AF3.8000600@mow.siemens.ru \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=lordzork@lordzork.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).