11-05-2008
- use of `init 6` will give the cleanest and orderly reboot (init informs svc.startd of the runlevel change and will move to the appropriate milestone).
- use of `shutdown -y -g0 -i6 **message**` will invoke init as well as give you grace period and messages to user (shutdown invoked the same as init above).
- halt,reboot,poweroff will not run any of the shutdown scripts and should be last resort.
10 More Discussions You Might Find Interesting
1. Solaris
I have a really strange issue on Solaris 10 running on v490. I'm running Oracle 10g on the box. Everything runs fine and all of a sudden I get a call from a DBA. I check and none of the Oracle processes are running. They were definitely running after the system booted and nobody stopped them. I try... (0 Replies)
Discussion started by: GKnight
0 Replies
2. Solaris
I am trying to install Solaris 10 on a target machine which is t1000. ( sun4v). I have configured my jumpstart server to install solaris over WAN. when i boot my machine, the wanboot image gets downloaded properly, miniroot gets downloaded properly, but after that the process fails with the... (3 Replies)
Discussion started by: hemalsid
3 Replies
3. Linux
Dear all,
I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel):
1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins
So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies
4. Red Hat
I encountered a problem on one of our database servers.
OS: CentOS 5.5 final
Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel)
We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies
5. Solaris
Hello all,
Fairly simple question here. I know that in Solaris 10 there is a way to tell a system running solaris 10 to init 0 and then boot disk1 all in the same command line from a SSH window. That way once you hit enter it then performs the init 0 and then does the boot disk1. ... (2 Replies)
Discussion started by: tording99z28
2 Replies
6. Solaris
Dears
Kindly am requested to collect the date histroy that the system was rebooted, so is there any log file or command that i can find the time that the system was rebooted?
thanks a lot for you kind support. (2 Replies)
Discussion started by: thehero
2 Replies
7. Solaris
i want to restart samba service in solaris 1o installed on virtual machine
but under
under /etc/init.d directory there is no folder with name samba in solaris 10
how do i proceed ? (4 Replies)
Discussion started by: rehantayyab82
4 Replies
8. Solaris
Hi,
we have a sun sparc solaris 10 machine and recently there was a power failure and one of the server domain was down. So today morning i have powered up the domain and it returned me to ok prompt then i have booted the machine with disk from devalias, the system was up as normal and no error... (0 Replies)
Discussion started by: phanidhar6039
0 Replies
9. UNIX for Advanced & Expert Users
Hi, I recently had an issue and by mistake a script of mine has initiated init 6 command,
Is there a way to stop the reboot manually after init 6 is given,
Your response is highly appreciated.
Thanks in advance !! (9 Replies)
Discussion started by: nanz143
9 Replies
10. Solaris
Dear all,
I have a solaris 10 in my environment (VMware virtual machine). recently I increased the harddisk size from the VMware and reboot my server. after reboot the os is unable to boot and gives the below error message.
exec(/sbin/init) file not found
press any key to restart
... (3 Replies)
Discussion started by: krishna001
3 Replies
HALT(8) Linux System Administrator's Manual HALT(8)
NAME
halt, reboot, poweroff - stop the system.
SYNOPSIS
/sbin/halt [-n] [-w] [-d] [-f] [-i] [-p] [-h]
/sbin/reboot [-n] [-w] [-d] [-f] [-i]
/sbin/poweroff [-n] [-w] [-d] [-f] [-i] [-h]
DESCRIPTION
Halt notes that the system is being brought down in the file /var/log/wtmp, and then either tells the kernel to halt, reboot or power-off
the system.
If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked
instead (with the -h or -r flag). For more info see the shutdown(8) manpage.
The rest of this manpage describes the behaviour in runlevels 0 and 6, that is when the systems shutdown scripts are being run.
OPTIONS
-n Don't sync before reboot or halt. Note that the kernel and storage drivers may still sync.
-w Don't actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file).
-d Don't write the wtmp record. The -n flag implies -d.
-f Force halt or reboot, don't call shutdown(8).
-i Shut down all network interfaces just before halt or reboot.
-h Put all hard drives on the system in stand-by mode just before halt or power-off.
-p When halting the system, switch off the power. This is the default when halt is called as poweroff.
DIAGNOSTICS
If you're not the superuser, you will get the message `must be superuser'.
NOTES
Under older sysvinit releases , reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if
the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when
/var/run/utmp hasn't been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to
do a hard halt or reboot.
The -h flag puts all hard disks in standby mode just before halt or power-off. Right now this is only implemented for IDE drives. A side
effect of putting the drive in stand-by mode is that the write cache on the disk is flushed. This is important for IDE drives, since the
kernel doesn't flush the write cache itself before power-off.
The halt program uses /proc/ide/hd* to find all IDE disk devices, which means that /proc needs to be mounted when halt or poweroff is
called or the -h switch will do nothing.
AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
SEE ALSO
shutdown(8), init(8)
Nov 6, 2001 HALT(8)