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 11:19:35 -0700 [thread overview]
Message-ID: <20040502181935.GA30249@taniwha.stupidest.org> (raw)
In-Reply-To: <20040502190425.E17905@flint.arm.linux.org.uk> <20040502190115.D17905@flint.arm.linux.org.uk>
On Sun, May 02, 2004 at 07:01:15PM +0100, Russell King wrote:
> As I read the original problem, you have gdm running on what it
> thought was a free tty at the time. agetty starts up and takes
> control of the tty.
Heh, I wasn't thinking about gdm, I was thinking more about rogue
programs keeping the tty open after the user has gone.
On Sun, May 02, 2004 at 07:04:25PM +0100, Russell King wrote:
> Oh, and also on this note, vhangup may be a good idea just before
> displaying the issue message.
I was more concerned about security issues with an evil program
hanging out. Since login is actually where the password is read and
it does use vhangup, then we don't need to worry.
So yes, using tty locking would seem the the sensible solution.
--cw
next prev parent reply other threads:[~2004-05-02 18:19 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
2004-05-02 18:01 ` Russell King
2004-05-02 18:04 ` Russell King
2004-05-02 18:19 ` Chris Wedgwood [this message]
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=20040502181935.GA30249@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®