After instruction from Joey Hess, booted into inti=/bin/sh and determined that it might not be a display issue -- my untrained eye interprets the logs as showing a spontaneous reboot of the system initiated right after the cron jobs start running, and the monitor shutdown is just a symptom of this. The hardware itself does not complete the shutdown/reboot process.
The last entries of dmesg before I did a reboot via reset button look like this: Aug 9 22:57:45 localhost /usr/sbin/cron[984]: (CRON) INFO (pidfile fd = 3) Aug 9 22:57:45 localhost /usr/sbin/cron[985]: (CRON) STARTUP (fork ok) Aug 9 22:57:45 localhost /usr/sbin/cron[985]: (CRON) INFO (Running @reboot jobs) So far, so good, since that matches the last entries in my log now, with my current (emergency) session running. But then we immediately get: Aug 9 22:57:45 localhost shutdown[998]: shutting down for system reboot Aug 9 22:57:45 localhost init: Switching to runlevel: 6 Aug 9 22:57:49 localhost kernel: Kernel logging (proc) stopped Aug 9 22:57:49 localhost kernel: Kernel log daemon terminating. Aug 9 22:57:49 localhost exiting on signal 15 Time passes, then I get up and hit the reset switch. The next entry is: Aug 9 23:46:30 localhost syslogd 1.4.1#15: restart. Could not find any interesting errors in the logs; am currently stumped, and willing to try anything that doesn't make my other partitions blow up. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
