From: Willy Tarreau <w@1wt.eu>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: david@lang.hm, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Vegard Nossum <vegard.nossum@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.3: su gets stuck for root
Date: Tue, 20 May 2008 22:38:33 +0200 [thread overview]
Message-ID: <20080520203833.GA6749@1wt.eu> (raw)
In-Reply-To: <483333E8.1090200@t-online.de>
On Tue, May 20, 2008 at 10:26:16PM +0200, Harald Dunkel wrote:
> david@lang.hm wrote:
> >
> >try killing syslog and then see if you continue to have the problem.
> >It's possible that what's happening is syslog is getting stuck and su is
> >sitting waiting for syslog to process the log entry.
> >
>
> No improvement: I killed syslogd, and yet stty gets stuck.
>
> But surely it was a smart idea.
have you checked in /proc/$(pidof stty)/fd/ to see if stty is bound to
any particular file descriptor ? Maybe you'll find the source of the
blocking operation here. You can find a unix socket attached to
another process, it may be a tty, a pipe, or even a device (eg:
/dev/random when there is no entropy left). Same for "su" BTW.
Regards,
willy
next prev parent reply other threads:[~2008-05-20 20:39 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 6:17 2.6.25.3: su gets stuck for root Harald Dunkel
2008-05-13 6:47 ` Vegard Nossum
2008-05-13 17:43 ` Harald Dunkel
2008-05-13 19:46 ` Willy Tarreau
2008-05-14 4:55 ` Harald Dunkel
2008-05-14 5:46 ` Willy Tarreau
2008-05-14 7:34 ` Vegard Nossum
2008-05-14 17:05 ` Harald Dunkel
2008-05-14 17:17 ` Vegard Nossum
2008-05-14 17:35 ` Alan Cox
2008-05-18 17:56 ` Harald Dunkel
2008-05-18 17:51 ` Alan Cox
2008-05-20 19:01 ` Harald Dunkel
2008-05-20 19:12 ` david
2008-05-20 20:26 ` Harald Dunkel
2008-05-20 20:38 ` Willy Tarreau [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-02 1:31 Joe Peterson
2008-06-02 5:12 ` Harald Dunkel
2008-06-02 5:32 ` Willy Tarreau
2008-06-02 5:55 ` Joe Peterson
2008-06-02 8:10 ` Alan Cox
2008-06-02 9:01 ` David Newall
2008-06-02 9:20 ` Alan Cox
2008-06-02 10:16 ` Vegard Nossum
2008-06-02 10:39 ` Vegard Nossum
2008-06-02 10:52 ` Alan Cox
2008-06-02 10:57 ` Vegard Nossum
2008-06-02 12:28 ` Alan Cox
2008-06-02 14:31 ` Vegard Nossum
2008-06-02 10:50 ` Alan Cox
2008-06-17 15:32 ` Joe Peterson
2008-06-02 15:26 ` Joe Peterson
2008-06-02 15:51 ` Alan Cox
2008-06-02 16:03 ` Joe Peterson
2008-06-04 14:43 ` Joe Peterson
2008-06-04 15:16 ` Alan Cox
2008-06-04 16:52 ` Joe Peterson
2008-06-04 17:10 ` Alan Cox
2008-06-04 20:32 ` Joe Peterson
2008-06-11 14:04 ` Joe Peterson
2008-06-12 11:52 ` Vegard Nossum
2008-06-14 1:49 ` Joe Peterson
2008-06-14 7:45 ` Vegard Nossum
2008-06-14 17:43 ` Joe Peterson
2008-06-14 20:34 ` Vegard Nossum
2008-06-14 20:52 ` Joe Peterson
2008-06-14 21:26 ` Vegard Nossum
2008-06-14 21:34 ` Joe Peterson
2008-06-02 5:42 ` 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=20080520203833.GA6749@1wt.eu \
--to=w@1wt.eu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david@lang.hm \
--cc=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/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