Messages in this thread | | | From | Gene Heskett <> | Subject | Re: amanda vs 2.6 | Date | Wed, 26 Nov 2003 15:41:35 -0500 |
| |
On Wednesday 26 November 2003 15:07, William Lee Irwin III wrote: >On Wed, 26 Nov 2003, William Lee Irwin III wrote: >>> Okay, then we need to figure out what the hung process was doing. >>> Can you find its pid and check /proc/$PID/wchan? > >On Wed, Nov 26, 2003 at 12:04:56PM -0800, Linus Torvalds wrote: >> I've seen this before, and I'll bet you 5c (yeah, I'm cheap) that >> it's trying to log to syslogd. >> And syslogd is stopped for some reason - either a bug, a mistaken >> SIGSTOP, or simply because the console has been stopped with a >> simple ^S. That won't stop "su" working immediately - programs can >> still log to syslogd until the logging socket buffer fills up. >> Which can be _damn_ frsutrating to find (I haven't seen this >> behaviour lately, but I remember being perplexed like hell a long >> time ago). > >That'll do it. Gene, could you check on syslogd too, then? > See my reply to Linus. > >-- 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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |