Messages in this thread | ![/](/images/icornerl.gif) | | Date | Wed, 26 Nov 2003 22:34:55 +0100 | From | Diego Calleja García <> | Subject | Re: amanda vs 2.6 |
| |
El Wed, 26 Nov 2003 12:04:56 -0800 (PST) Linus Torvalds <torvalds@osdl.org> escribió:
> 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).
I've seen this too. I could fix it with "sysrq + s". I always though it was a bug in syslogd. I haven't seen it in a while...
Diego Calleja - 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/
| ![\](/images/icornerr.gif) |