12-09-2009
hello
the runlevel that the unix system boots into is determined by the configuration file
/etc/inittab.
this file is read by the init (process) before booting the file .
You can edit the file to determine which runlevel you want to boot (permanently )
check the manual of the OS to locate that file or the file with similar properties.
Regards.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
Quick question.
Does anyone know what is the compination of buttons that I have to press to stop the start up so I can bring the system in a single user mode?
I use HP Vis 9000
Thanks alot (1 Reply)
Discussion started by: guest100
1 Replies
2. UNIX for Dummies Questions & Answers
All,
Does anybody know of a Unix command or file name where I can find out when the Unix box was last rebooted?
We're using HP-UX 10.2.
Thanks,
PP (3 Replies)
Discussion started by: Positive Parrot
3 Replies
3. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
4. Shell Programming and Scripting
Hi
What is the best way to reboot a Linux computer?
i) Press the power switch
ii) type 'init 6' as any user, then enter the root password when prompted
iii) Pour metal filings in the top of the computer.
iv) su to root then type 'init 6' (6 Replies)
Discussion started by: tjay83
6 Replies
5. SCO
Hi,
We are using SCO UNIX 7.1.3 and the server recently started rebooting by itself.
Do anyone know how can i create a dump or crash dump while the server rebooots?
Your quick help on this is really appreciated.
Regards,
Ravikumar R (1 Reply)
Discussion started by: rrb2009
1 Replies
6. Solaris
One of my X4600 server had a power loss and rebooted and now its giving me a strange problem servers internal disk controller naming has changed by itself ... the after failsafe boot md.conf file shows following c3txdx but shows internal disk at c4txdx ... what could be the reason for this and... (1 Reply)
Discussion started by: fugitive
1 Replies
7. Solaris
Hi ,
Everytime after reboot when user tries to start vnc below error is thrown
$ vncserver :5
Couldn't start Xvnc; trying default font path.
Please set correct fontPath in the vncserver script.
Couldn't start Xvnc process.
_XSERVTransSocketCreateListener: failed to bind listener... (7 Replies)
Discussion started by: chidori
7 Replies
8. Shell Programming and Scripting
Hi guys
I am troubleshooting a script that informs me when a system has rebooted.
The script is placed in /etc/rc3.d folder under root.
The script is as follows:
. /opt/scripts/function.sh
PATH=/usr/bin
EMAIL_ADD=<email address> ... (2 Replies)
Discussion started by: Junaid Subhani
2 Replies
9. IP Networking
I'm trying to figure out what circumstances would cause an Open Solaris 11.2 host to switch itself from a static to a DHCP ip address upon reboot. This has only happened once but is a cause for some concern as this machine will be part of a web server pool.
Nothing has changed on the LAN that... (2 Replies)
Discussion started by: SmokeyJoe
2 Replies
10. Linux
Respected Members,
We encountered an issue during node reboot when eth1 and eth5 of bond1 were behaving unusual(both eth1 and eth5 were in unknown states and ifdown and ifup were used to rectify). Please find the messages and configuration files as below and please let me know for any other... (0 Replies)
Discussion started by: Mudit Bansal
0 Replies
LEARN ABOUT MOJAVE
runlevel
RUNLEVEL(8) runlevel RUNLEVEL(8)
NAME
runlevel - Print previous and current SysV runlevel
SYNOPSIS
runlevel [options...]
OVERVIEW
"Runlevels" are an obsolete way to start and stop groups of services used in SysV init. systemd provides a compatibility layer that maps
runlevels to targets, and associated binaries like runlevel. Nevertheless, only one runlevel can be "active" at a given time, while systemd
can activate multiple targets concurrently, so the mapping to runlevels is confusing and only approximate. Runlevels should not be used in
new code, and are mostly useful as a shorthand way to refer the matching systemd targets in kernel boot parameters.
Table 1. Mapping between runlevels and systemd targets
+---------+-------------------+
|Runlevel | Target |
+---------+-------------------+
|0 | poweroff.target |
+---------+-------------------+
|1 | rescue.target |
+---------+-------------------+
|2, 3, 4 | multi-user.target |
+---------+-------------------+
|5 | graphical.target |
+---------+-------------------+
|6 | reboot.target |
+---------+-------------------+
DESCRIPTION
runlevel prints the previous and current SysV runlevel if they are known.
The two runlevel characters are separated by a single space character. If a runlevel cannot be determined, N is printed instead. If neither
can be determined, the word "unknown" is printed.
Unless overridden in the environment, this will check the utmp database for recent runlevel changes.
OPTIONS
The following option is understood:
--help
Print a short help text and exit.
EXIT STATUS
If one or both runlevels could be determined, 0 is returned, a non-zero failure code otherwise.
ENVIRONMENT
$RUNLEVEL
If $RUNLEVEL is set, runlevel will print this value as current runlevel and ignore utmp.
$PREVLEVEL
If $PREVLEVEL is set, runlevel will print this value as previous runlevel and ignore utmp.
FILES
/run/utmp
The utmp database runlevel reads the previous and current runlevel from.
SEE ALSO
systemd(1), systemd.target(5), systemctl(1)
systemd 237 RUNLEVEL(8)