> Oops are already logged to kernel log. But if klogd or syslogd are not
> running then the Oops never gets written to disk. Alas this occurs all
> too often. Mind you, the real problem is that users do not read
> Documentation/oops-tracing.txt. I don't think that there is a
> programming solution for that :(.
+ printk("Read /usr/src/linux/Documentation/oops-tracing.txt!\n");
....would be a start.
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."
- 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/