mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Joe Peterson <joe@skyrush.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tty: ctrl-c not always echoed, especially under load
Date: Thu, 7 Aug 2008 20:37:16 +0100	[thread overview]
Message-ID: <20080807203716.4a9870f6@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <489A06D9.1080600@skyrush.com>

On Wed, 06 Aug 2008 14:17:29 -0600
Joe Peterson <joe@skyrush.com> wrote:

> Alan Cox wrote:
> > If the output buffer is full then echoed characters/^C etc will vanish the
> > way n_tty implements its buffering internally. It's always worked that
> > way.
> 
> One more observation:
> 
> In Linux, try this:
> 
> # cat > foo
> hi^Sthere^Q
> ^D
> 
> (in other words, during the cat into "foo", type "hi", hit ^S, then type
> "there", then hit ^Q, then, on the next line, ^D to end the file)
> 
> Note that the "there" does not appear after hitting ^Q, but it does
> appear in the file.  So the characters were accepted, but they were not
> echoed (not even saved for echo when the terminal is restarted).
> 
> This behavior differs from that of FreeBSD (just tried it for fun -
> haven't tried other Unix's yet).  I have noticed other times that the
> echo seems to get lost while the tty is stopped.  Not sure if all this
> is related, but something seems amiss.  Thoughts?

It should certainly occur if the output buffer is full but that shouldn't
be the case for a few bytes. Agreed the current behaviour is unexpected
and less than desirable so hack away.


  reply	other threads:[~2008-08-07 19:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 22:03 Joe Peterson
2008-08-04 23:11 ` Alan Cox
2008-08-04 23:36   ` Joe Peterson
2008-08-06 20:17   ` Joe Peterson
2008-08-07 19:37     ` Alan Cox [this message]
2008-08-07 20:31       ` Joe Peterson
2008-08-11 15:14       ` Joe Peterson
2008-08-11 16:39         ` Alan Cox
2008-08-11 17:41           ` Joe Peterson
2008-08-14 16:19           ` [PATCH] " Joe Peterson

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=20080807203716.4a9870f6@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=joe@skyrush.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®