linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amanda vs 2.6
Date: Wed, 26 Nov 2003 15:23:33 -0500	[thread overview]
Message-ID: <200311261523.33524.gene.heskett@verizon.net> (raw)
In-Reply-To: <20031126195049.GT8039@holomorphy.com>

On Wednesday 26 November 2003 14:50, William Lee Irwin III wrote:
>On Wednesday 26 November 2003 14:30, William Lee Irwin III wrote:
>>> Sounds like trouble. Are there any external signs of what's going
>>> on? e.g. is the disk thrashing?
>
>On Wed, Nov 26, 2003 at 02:43:43PM -0500, Gene Heskett wrote:
>> No, it just hangs forever on the su command, never coming back.
>> everything else I tried, which wasn't much, seemed to keep on
>> working as I sent that message with that hung su process in
>> another shell on another window.  I'm an idiot, normally running
>> as root... I've rebooted, not knowing if an echo 0 to that
>> variable would fix it or not, I see after the reboot the default
>> value is 0 now.
>
>Okay, then we need to figure out what the hung process was doing.
>Can you find its pid and check /proc/$PID/wchan?
>
Ok, repeat, us is PID 1843, so:
[root@coyote root]# ps -ea|grep su
 1843 pts/1    00:00:00 su
[root@coyote root]# cat /proc/1843/wchan
sys_wait4[root@coyote root]#

Unforch, echoing a 0 to that variable doesn't fix it, reboot time 
again.

Do you need my .config?

>
>-- wli

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


  parent reply	other threads:[~2003-11-26 20:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 17:12 amanda vs 2.6 Gene Heskett
2003-11-26 17:19 ` William Lee Irwin III
2003-11-26 19:15   ` Gene Heskett
2003-11-26 19:30     ` William Lee Irwin III
2003-11-26 19:43       ` Gene Heskett
2003-11-26 19:50         ` William Lee Irwin III
2003-11-26 20:04           ` Linus Torvalds
2003-11-26 20:07             ` William Lee Irwin III
2003-11-26 20:41               ` Gene Heskett
2003-11-26 20:40             ` Gene Heskett
2003-11-26 20:56             ` Chris Adams
2003-11-26 21:34             ` Diego Calleja García
2003-11-27  8:41             ` Nick Piggin
2003-11-27 10:05               ` Gene Heskett
2003-11-27 13:39                 ` William Lee Irwin III
2003-11-27 17:16                   ` Gene Heskett
2003-11-27 17:55                     ` Gene Heskett
2003-11-27 18:04                       ` Gene Heskett
2003-11-29 17:14                   ` Gene Heskett
2003-12-01 18:43                     ` Mike Fedyk
2003-12-02  2:41                       ` Gene Heskett
2003-12-07 11:56                         ` Paul P Komkoff Jr
2003-12-07 13:53                           ` Gene Heskett
2003-11-26 20:23           ` Gene Heskett [this message]
2003-11-26 20:32             ` William Lee Irwin III
2003-11-26 20:47               ` Gene Heskett

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=200311261523.33524.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).