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
reboot(1M) reboot(1M)
NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
The following options are supported:
-d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync
filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to
sync filesystems.
-q Quick. Reboot quickly and ungracefully, without shutting down running processes first.
The following operands are supported:
boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel
upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are
specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the
boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot
argument list.
Example 1: Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2: Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
/var/adm/wtmpx login accounting file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown
of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
11 Apr 2005 reboot(1M)