Sponsored Content
Full Discussion: sun system not starting up
Top Forums UNIX for Dummies Questions & Answers sun system not starting up Post 773 by 98_1LE on Wednesday 17th of January 2001 02:51:41 PM
Old 01-17-2001
While I am no expert it sounds like it's hanging up at the init script /etc/rc2.d/S72inetsvc. You can try pressing stop-a to get the ok prompt, then typing boot -s to enter single user mode. From there cd to /etc/rc2.d Hand execute
./S69init start
From there do the same for each file starting with an "S" higher than S69
./S71rpc start
etc...
This will narrow down where the problem is. I'm sure someone will have a better reply soon.
 

3 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Starting sun raid manager for A1000

Can anyone tell me the syntax for starting Raid manager on a A1000? (2 Replies)
Discussion started by: MBGPS
2 Replies

2. Solaris

System not starting completely

I have an Ultra 60, running Solaris 5.8. During boot all of a sudden it dies after Yp comes up then the netmasks are set and then I don't see anything any more. How do I tell whats causing it to hang at this point. I can login to it but can't tell what preocess is hung. /var/adm/messages has no... (7 Replies)
Discussion started by: frankkahle
7 Replies

3. IP Networking

Starting Home System with a Firewall

I'm a beginner to Unix System Administration and I'd like to start first by having a server setup as a firewall. What would be a good distro to do this with? I'll be running it on an old computer. I plan on using command line only with this box. Also, where can I start reading about doing this?... (2 Replies)
Discussion started by: tr33
2 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 04:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy