05-13-2014
Quote:
Originally Posted by
Corona688
This would not work, because 'init 6' does nothing but send a signal of some sort to the real init process, the one which started when the computer booted. You'd have a fraction of a millisecond to catch 'init 6' before it sends that signal and quits.
Killing the real init process would make things worse.
That is good to know in case I do type init 6 as root on a unix system. The other problem with someone accidentally doing init 6, is that even if you can stop the shutdown from happening, the OS will start killing processes. Processes that would need to be restarted. Either way doing init 6 or shutdown on a running production server by accident is going to cause issues.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Expert,
I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0..
I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies
2. 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
3. UNIX for Advanced & Expert Users
Hi ,
I have one question, suppose i am a normal user and when i use 'w' command , it shows who is logged on and what they are doing .
Now i want to stop others users to know what i am doing accept the root ?
can i do this ?
thanks (5 Replies)
Discussion started by: mobile01
5 Replies
4. Solaris
Hi All,
Does anyone tell me , is there any difference between solaris "reboot " and init 6 ...bcos in case of reboot for a system ..can i use init 6 for that instead.
Thanks in advance,
J (6 Replies)
Discussion started by: jegaraman
6 Replies
5. 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
6. Red Hat
What is the difference between 'init s' and 'init 1'.
I know that both will work to change the current run level to single user mode.
Is there any difference in those two commands? (5 Replies)
Discussion started by: praveen_b744
5 Replies
7. Shell Programming and Scripting
We have number of servers which belongs to platforms Solaris, AIX,HP-UX and LINUX. Monitoring tool 'Patrol Agent' process run on the servers to check for the server health and communicate with the Patrol server through the port 5181. During scheduled reboot and maintenance of servers we do receive... (1 Reply)
Discussion started by: subharai
1 Replies
8. UNIX for Advanced & Expert Users
Hi,
I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS.
When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies
9. Solaris
i did my research in finding the answer but couldn't find right one. Please give your inputs. (6 Replies)
Discussion started by: ranumala
6 Replies
10. 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
LEARN ABOUT CENTOS
runit-init
runit-init(8) System Manager's Manual runit-init(8)
NAME
init - a UNIX process no 1
SYNOPSIS
init [ 0 | 6 ]
DESCRIPTION
runit-init is the first process the kernel starts. If runit-init is started as process no 1, it runs and replaces itself with runit(8).
If runit-init is started while the system is up, it must be either called as init 0 or init 6:
init 0 tells the Unix process no 1 to shutdown and halt the system. To signal runit(8) the system halt request, runit-init removes all
permissions of the file /etc/runit/reboot (chmod 0), and sets the execute by owner permission of the file /etc/runit/stopit (chmod
100). Then a CONT signal is sent to runit(8).
init 6 tells the Unix process no 1 to shutdown and reboot the system. To signal runit(8) the system reboot request, runit-init sets the
execute by owner permission of the files /etc/runit/reboot and /etc/runit/stopit (chmod 100). Then a CONT signal is sent to
runit(8).
EXIT CODES
runit-init returns 111 on error, 0 in all other cases.
SEE ALSO
runit(8), runsvdir(8), runsvchdir(8), sv(8), runsv(8), chpst(8), utmpset(8), svlogd(8)
http://smarden.org/runit/
AUTHOR
Gerrit Pape <pape@smarden.org>
runit-init(8)