public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Peterson <joe@skyrush.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tty: ctrl-c not always echoed, especially under load
Date: Wed, 06 Aug 2008 14:17:29 -0600	[thread overview]
Message-ID: <489A06D9.1080600@skyrush.com> (raw)
In-Reply-To: <20080805001129.72d06e60@lxorguk.ukuu.org.uk>

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?

					Thanks, Joe

  parent reply	other threads:[~2008-08-06 20:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 22:03 tty: ctrl-c not always echoed, especially under load Joe Peterson
2008-08-04 23:11 ` Alan Cox
2008-08-04 23:36   ` Joe Peterson
2008-08-06 20:17   ` Joe Peterson [this message]
2008-08-07 19:37     ` Alan Cox
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=489A06D9.1080600@skyrush.com \
    --to=joe@skyrush.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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