To Respond to a Process Suspend Failure
Select Cancel when the Suspend Failed window appears with the following message: Process cannot be stopped
If you have not already saved your work, do so now. Try to suspend again.
Check for more information in the Console window in the Workspace.
If a process is a real-time process or is performing certain special network operations, that process might refuse to suspend gracefully. In most cases, this is only a temporary condition that you can correct by trying to suspend again.
However, if the problem persists, stop the offending process, as specified in the console message, and try to suspend again.
Try Suspend again.
If Suspend succeeds, the system saves your activities and the system powers off.
If Suspend does not succeed, the alert window is displayed again.
Caution - Save your work if you have not already done so.Select Power Off.
Your data is not saved unless you save the data manually.
When you power on again, your system automatically reboots.
To Respond to an Abnormal Condition
Select Cancel when the Suspend Failed window appears with the following message: Abnormal condition during suspend,
You must take corrective action before you can try to suspend again.
If you have not already saved your work, do so now.
Check for more information in the Console window in the Workspace.
You might be able to take further corrective action by checking the console error messages.
Try Suspend again.
If Suspend succeeds, the system saves your activities and the system powers off.
If Suspend does not succeed, the alert window is displayed again. In this case, continue with the next step.
Caution - Save your work if you have not already done so.Select Power Off.
Your data is not saved unless you save the data manually.
When you power on again, your system automatically reboots.
Troubleshooting a Shortage of Disk Space
When you execute a Suspend command, your system creates a statefile to preserve the current state of your system. If the file system that contains the statefile is full, a Suspend Failed window appears with the following message:
Suspend requires more disk space for statefile.
Perform the following procedure in response to this message.
To Respond to a Disk Space Limitation
Select Cancel.
You must take corrective action before you can try to suspend again.
If you have not already saved your work, do so now.
Check for more information in the Console window in the Workspace.
You must have a minimum of 10 Mbytes of free space. Clean up a partition before you try to suspend again. Another solution is to change the location of the statefile to a file system with sufficient space, as described in the power.conf(4) man page.
Contact your system administrator for assistance, if necessary.
Try Suspend again.
If Suspend succeeds, the system saves your activities and the system powers off.
If Suspend does not succeed, the alert window appears again. In that case, continue with the next step.
Caution - Save your work if you have not already done so.Select Power Off.
Your data is not saved unless you save the data manually.
When you power on again, your system automatically reboots.
Disabling the Screen Lock
After a Resume, the system screen lock is invoked by default. To disable the screen lock before you use the power key to Suspend, use the following procedure.
Note - You cannot disable screen locking that is put into effect by AutoShutdown. This is a security feature. It ensures that only someone who knows your password can get access to your work session when the system resumes.
To Disable the Screen Lock After Using the Power Key to Suspend
Modify the speckeysd.map file to add the -x flag to the sys-suspend entry.
For more information, see the man page for speckeysd.map(4).
Caution - Save your work if you have not already done so.Exit the current windowing session and restart.
In place of this step, you may also kill the speckeysd daemon and then restart the daemon.