http://qa.mandrakesoft.com/show_bug.cgi?id=5354
------- Additional Comments From [EMAIL PROTECTED] 2003-07-09 18:35 ------- Version-Release number of selected component (if applicable): All versions in all linux distributions How reproducible: Always Steps to Reproduce: 1. Power off running machine without shutdown to simulate sudden loss of power 2. Restart machine 3. Headless servers will hang on any difficulties even if the root filesystem was successfully checked (PASSED/REBOOT return codes) Actual Results: Headless machine hung until user input supplied. Expected Results: Headless machine should have restarted automatically. Additional info: This can cause an inability to restart headless machines after a power failure or severe problem without attaching a monitor and keyboard even if the disk was successfully repaired. I have created a patch that successfully recovers a headless machine EVERY TIME when ever the errors are trivial and does not require user input if /etc/sysconfig/autofsck contains PROMPT="no" Also, if the power failure causes a loss of power before proper shutdown occurrs, the headless machine defaults to a power failure status and does not allow logins until a monitor is attached. My patch also deals with this correctly. I feel this patch is instrumental in acheiving lowered TOC for server farms as well as user desktop machines since it should be possible to autocorrect for most problems without user intervention. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: rc.sysinit when checking for filesystem integriry fails miserably on headless machines even when the PROMPT value is set to "no". Any error unexpected return value in the root file system demands user input. Also, the return code from fsck is not interpreted correctly - fsck returns a bitfield - rc.sysinit instead compares the error level as if it were a regular integer. There is much duplicated script code for handling fsck issues. rc.sysinit does not handle an interrupted powerfail shut down.
