Sponsored Content
Full Discussion: System Hanging on boot
Operating Systems AIX System Hanging on boot Post 302259123 by bbbngowc on Monday 17th of November 2008 10:13:51 AM
Old 11-17-2008
I looked in the inittab file for the lines relating to "Single User Mode" but I couldn't see it. Can you be a little more specific as to where it is? Also, there is not /etc/rc.log file. At least not on this particular box.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

System boot configuration

On my PC I have two hard disks, the first with Windows 98 SE and the second with Linux Mandrake 8.0 (Traktopel). When I have installed Linux, it has modified the boot record of the 1st HD and it has added a graphic menu (LILO) for selecting the OS to use. By default, if I don't press a key, Linux... (2 Replies)
Discussion started by: robotronic
2 Replies

2. UNIX for Dummies Questions & Answers

Boot from a remote system

I have a diskless work station. i want to boot from a remote linux machine. what changes i will have to do in configuration. Plz tell me thanks (1 Reply)
Discussion started by: hemant29
1 Replies

3. SCO

Can't boot system--help

I get a message saying Not enough space to dump xxxxx pages Press any key to reboot Safe to power off After rebooting it never gets to the "Press CTRL D to continue or enter password for single user" message before it goes back to "Not enough space..." message above. Vicious cycle. ... (0 Replies)
Discussion started by: deloev
0 Replies

4. SuSE

ssh command on remote linux system hanging

Hi, Our systems: system1: amd 64 running suse linux 9 enterprize system2: amd 64 running esx vmware 3 with suse linux 9 enterprize. The problem is: when we ssh into system2 and execute the command: ls -al the session hangs. Infact session hangs when we execute any... (3 Replies)
Discussion started by: rajranibl
3 Replies

5. UNIX for Dummies Questions & Answers

help boot system erro

being nosey on sons laptop and set a password and now need to undo this but its in the boot system :eek::eek::eek: (4 Replies)
Discussion started by: hempel
4 Replies

6. Solaris

System boot up log file

Hi, where can I check the system boot up log file like those message when the system booting up.... Thanks. (14 Replies)
Discussion started by: efang
14 Replies

7. AIX

Hanging in the system after login !

Guy's I have AIX 6.1 has some slowness when I login to the system .. When I login by user screen hangs for some time 20 seconds then it's give me the command prompt .. ! system is fine is working fine only this issue I faced can you please help me in this .. what's the expected reason... (2 Replies)
Discussion started by: ITHelper
2 Replies

8. Solaris

System will not boot

We have a system that won't boot. It is Sun V245 that was patched yesterday with the latest Recommended 10 patch cluster. I will post what we get during the boot at the end of the email message. We have tried rebuilding the bootblk, booting from the cdrom, and running an fsck, booting into failsafe... (2 Replies)
Discussion started by: brownwrap
2 Replies

9. Red Hat

System fail to boot

Hi im using centos 6.4 starting yesterday i have a strange issue that im unable to resolve. the system is booting to GRUB menu and the os is not starting. i tried to run a repair install and the message attached is what i get, what can cause this? thanks, (1 Reply)
Discussion started by: guy3145
1 Replies

10. UNIX for Advanced & Expert Users

System cannot boot up

Hi, I got stuck in a very messy situation yesterday after attempting to resolve a filesystem full issue. The user reported that their filesystem (/var/DWS) was 100% full even after moving few files of sizes 14G, 30G and 50G out of the directory. I checked the filesystem once more after this... (5 Replies)
Discussion started by: anaigini45
5 Replies
inittab(4)						     Kernel Interfaces Manual							inittab(4)

NAME
inittab - Controls the initialization process SYNOPSIS
/etc/inittab DESCRIPTION
The inittab file provides the init program with instructions for creating and running initialization processes. The init program reads the inittab file each time init is invoked. The file typically contains instructions for the default initialization, the creation and control of processes at each run level, and the getty command, which controls the activation of terminal lines. Each line in the inittab file contains an entry that has four fields; each field is separated by a colon. There is no limit to the number of entries in the inittab file. The entry syntax is as follows: Identifier:Runlevel:Action:Command Specifies a fourteen character field used to uniquely identify an object. Specifies a twenty character field that defines the run levels in which the object is to be processed. Runlevel corresponds to a configuration of processes in a system. Each process spawned by the init command is assigned one or more run levels in which it is allowed to exist. The run levels are as follows: Specifies the halt state. Specifies multiuser state without network services. Specifies multiuser state with network services. Specifies single-user state. You can define multiple run levels for a process by specifying more than one run level character in any combination. Specifies a twenty char- acter field that tells init how to treat the specified process. init recognizes the following Action values: Specifies that if the process does not exist or if it dies, init starts it. If the process exists, init continues to process the inittab file. Specifies that if init enters a run level that matches the run level specified in the inittab file entry, it starts the process and waits for its termination. As long as init continues in this run level, it does not act on subsequent reads of the entry in the inittab file. Specifies that if init enters a run level that matches the run level specified in the inittab file, it starts the process and does not wait for its termination. When the process stops, init does not restart it. If init enters a new run level where the process is still running from a previous run- level change, init does not restart the process. Specifies that when init first executes and reads the inittab file, it processes this entry. The init program starts the process and does not wait for its termination. When the process stops, init does not restart it. The run level specified in this inittab file entry should be the default run level, or it must match the run level in which init operates at boot time. Specifies that when init first executes and reads the inittab file, it processes this inittab file entry. The init program starts the process, waits for its termination and, when it dies, does not restart the process. (This value exists only for SVID3/SVR4 com- patibility.) Specifies that if init receives the SIGPWR power fail signal, it executes the process associated with this line. (This value exists only for SVID3/SVR4 compatibility.) Specifies that if init receives the SIGPWR power fail signal, it executes the process associ- ated with this line and waits until the process terminates before continuing processing the inittab file. Specifies that if the process associated with this line is currently running, init sends the warning signal SIGTERM and waits 20 seconds before sending the kill signal SIGKILL. If the process does not existent, init ignores the inittab entry. Specifies that a line with this action is processed when init is originally invoked. The init program uses this line to determine the run level to enter originally. It determines this by taking the highest run level specified in the run level field and using that as its initial state. If the run level field is empty, this is inter- preted as 0s23, causing init to enter run level 3. If init does not find an initdefault entry in the inittab file, it requests an initial run level from the operator. Specifies that entries of this type are executed before init tries to access the console. This inittab file entry should be used only to initialize devices on which init could attempt to request a run level. Specifies a 1024 character field that contains the sh command to be executed. The command is prefixed with exec. Any legitimate sh syntax can appear in the command field. Com- ments can be inserted be specifying a number sign (#). The line continuation character can be placed at the end of a line. EXAMPLES
The following is an example of an inittab file entry for a terminal line: tty01:23:respawn:/usr/sbin/getty /dev/tty08 9600 vt100 FILES
Specifies the command that initializes and controls terminal lines. RELATED INFORMATION
Commands: init(8), getty(8) Functions: kill(2) delim off inittab(4)
All times are GMT -4. The time now is 04:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy