From: Chris Wedgwood <cw@f00f.org>
To: Andrew Morton <akpm@osdl.org>,
vandrove@vc.cvut.cz, koke@amedias.org,
linux-kernel@vger.kernel.org,
Andries Brouwer <Andries.Brouwer@cwi.nl>
Subject: Re: strange delays on console logouts (tty != 1)
Date: Sun, 2 May 2004 10:53:26 -0700 [thread overview]
Message-ID: <20040502175326.GA30108@taniwha.stupidest.org> (raw)
In-Reply-To: <20040502135424.GA20578@apps.cwi.nl> <20040502111729.D9605@flint.arm.linux.org.uk>
On Sun, May 02, 2004 at 11:17:29AM +0100, Russell King wrote:
> The first one is of particular note, because it is the cause of the
> GROSS hack in agetty, which according to the comments is also in
> gdm.
I've emailed the debian util-linux maintainer about this.
> I wonder really if the problem was elsewhere, and if Debian wanted
> to take care of this problem, why they didn't just take the serial
> line locking solution (really: s/serial line/tty/) and apply it to
> agetty / gdm.
It locking really the way to do this? What's wrong with vhangup?
On Sun, May 02, 2004 at 03:54:24PM +0200, Andries Brouwer wrote:
> However, my agetty source does not contain the string VT_OPENQRY. I
> suppose this is a private Debian change. Maybe you should contact
> Debian people to find out who did this and why.
Sorry, I used 'apt-get source' to get the source code and completely
forgot about the fact it would patch the package.
> (And/or try the vanilla agetty to see whether the problems go away.)
Vanilla will work as expected. It still doesn't seem to prevent the
case where someone could terminate and leave a process running that
would take input later on though... at least not that I can see.
Anyhow, this for not is clearly a userspace issue so sorry about all
the noise people.
--cw
next prev parent reply other threads:[~2004-05-02 17:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 19:53 Jorge Bernal
2004-05-01 21:46 ` Chris Wedgwood
2004-05-01 23:24 ` Petr Vandrovec
2004-05-01 23:44 ` Chris Wedgwood
2004-05-02 0:36 ` Petr Vandrovec
2004-05-02 0:45 ` Chris Wedgwood
2004-05-02 13:54 ` Andries Brouwer
2004-05-02 1:03 ` Andrew Morton
2004-05-02 8:00 ` Russell King
2004-05-02 8:13 ` Andrew Morton
2004-05-02 8:17 ` Russell King
2004-05-02 9:37 ` Russell King
2004-05-02 10:17 ` Russell King
2004-05-02 12:01 ` Petr Vandrovec
2004-05-02 17:53 ` Chris Wedgwood [this message]
2004-05-02 18:01 ` Russell King
2004-05-02 18:04 ` Russell King
2004-05-02 18:19 ` Chris Wedgwood
2004-05-01 22:20 ` Chris Wedgwood
2004-05-02 0:26 ` Jorge Bernal
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=20040502175326.GA30108@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=koke@amedias.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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®