Messages in this thread | | | From | Keith Owens <> | Subject | Re: Profanity in the Linux Kernel?!?!? | Date | Tue, 29 Jun 1999 12:10:59 +1000 |
| |
On Mon, 28 Jun 1999 20:29:29 +0100 (GMT), Riley Williams <rhw@MemAlpha.CX> wrote: >?? wrote > > What happens when due to some system malfunction, syslogd and/or > > klogd dies? Then nothing gets logged, and nothing gets printed. > >That happens often enough now, with exactly that result - just read >the constant stream of bug reports on linux-kernel where this has >clearly happenned, with precicely the result you quote... > >What we really could use is for inetd to auto-restart them if >something turns up for them to log...
It is fairly rare that syslogd or klogd actually die. What occurs far more often is that the scheduler croaks or disk I/O is unable to complete. The typical problem environment is one that ends in message "Scheduling in interrupt" or "Aiee, killing interrupt handler" and the entire machine is effectively dead. Doing an auto restart of syslogd or klogd does nothing for those cases.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |