Sponsored Content
Full Discussion: Power off on SCO 5.0.6
Operating Systems SCO Power off on SCO 5.0.6 Post 303014283 by jgt on Thursday 8th of March 2018 01:14:37 PM
Old 03-08-2018
Read the following section of the init command man page.
Code:
0                                                                            
       Shut the machine down so it is safe to remove the power.              
       Have the machine remove power if it can. This state can be            
       executed only from the console.                                       
       Note that init 0 should not be used if you have a USB                 
       keyboard attached to the console. During an init 0, the               
       USB stack gets shut down and the system then waits for a              
       keyboard keypress interrupt before rebooting. Since USB is            
       gone, there's no way for a keypress on the USB keyboard to            
       get serviced, and the system does not respond. If this                
       occurs, you must either press the hardware reset button or            
       power cycle the system.                                               
1                                                                            
       Put the system in single-user mode. Unmount all file                  
       systems except the root filesystem. All user processes are            
       killed except those connected to the console. It is                   
       recommended that this state be executed only from the                 
       console.                                                              
2                                                                            
       Put the system in multiuser mode. All multiuser                       
       environment terminal processes and daemons are spawned.               
   5                                                                            
          Stop the UNIX system and go to the firmware monitor.                  
   6                                                                            
          Stop the UNIX system and reboot to the run-level defined              
          by the initdefault entry in /etc/inittab.

The above is from the 6.0.0 documentation but is backwards compatible to Xenix.

---------- Post updated at 01:14 PM ---------- Previous update was at 01:09 PM ----------

If you are unable to power down the system, because the cmos does not support it, you may be able to create a workaround using a UPS that you can send a "power off in 5 minutes" command to just prior to shutting down the SCO system.
 

We Also Found This Discussion For You

1. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
init(8) 						      System Manager's Manual							   init(8)

NAME
init - Process control initialization SYNOPSIS
/sbin/init [0123456789MmQqSs] DESCRIPTION
The init program initializes the system by creating and controlling processes. The processes run by init at each run level are defined in the inittab file. The init program reads and processes the entries in the inittab file. The init program considers the system to be in a run level at any given time; each run level has a specific group of processes that run at that level. The init program operates in one of eleven run levels: 0-9 and Ss. Of these, only 0, s, 2, and 3 are configured in the inittab file by default. The run level changes when a privileged user invokes init. The new init sends appropriate signals to the original init that tell it which run level to change to. Running the init program is the last step in the boot process after the root file system is mounted. The init program scans the inittab file and looks for an entry with the initdefault keyword. If the entry is there, init uses the run level specified in that entry as the initial run level to enter. If the entry is not found in the inittab file or if the inittab file does not exist, init requests that the user enter a run level from the system console, /dev/console. If the user enters the letter s, init enters single user state, assigns the virtual console terminal to the user's terminal and opens it for reading and writing. The su command is invoked and the system displays a message on the console stating the location of the virtual console. To change the run level, the user specifies either the 0, 2, 3, or s flag. For the first post-boot execution of init to a run level other than single user, it searches the inittab file for entries at the new run level that have the boot or bootwait keywords. If the run level that is specified matches the entry, the init program acts on these entries before processing other entries in the inittab file. Any special initialization of the system, such as checking and mounting file systems, takes place before users are allowed on the system. The init program then scans the inittab file to find all entries that are to be handled for that level. Before starting a new process, init reads each entry in the inittab file, and for each entry that should be respawned, init forks a child process. After spawning all required processes, init waits for one of its descendant processes to stop, a power-fail signal, or a signal that it should change the run level. If one of the preceding three conditions occurs, init reexamines the inittab file. You can add new entries to the inittab file, but init does not reexamine the file until one of the three previous conditions actually occurs. To immedi- ately reexamine the inittab file, invoke the init program with the q flag. FLAGS
Shuts down and halts the system. Changes the run level to a multiuser state with local processes and daemons. Changes the run level to a multiuser state with remote processes and daemons. Changes run level to that specified by the number flag in the /etc/inittab file. If no such entry exists, no action is taken and no message is output. Moves control to the console device and halts to single-user mode. Forces init to reexamine the entries in the inittab file and terminates any live processes which have had their configuration entries removed from /etc/inittab. Users should be aware that when a getty(8) line has been removed from /etc/inittab, and a login shell is active on the ter- minal line that was formerly designated in inittab as a getty entry, the login shell will be killed. Changes the run level to a single user state with only the essential kernel services. FILES
Specifies the command path Specifies the init command control file Specifies the permanent login accounting file RELATED INFORMATION
Commands: getty(8), rc0(8), rc2(8), rc3(8), shutdown(8) Calls: kill(2), reboot(2) Files: inittab(4) delim off init(8)
All times are GMT -4. The time now is 10:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy