Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to stop a reboot after init 6 is given by mistake? Post 302901334 by gandolf989 on Tuesday 13th of May 2014 11:38:27 AM
Old 05-13-2014
I wonder if you could do "pf -ef | grep 'init 6'" then get the pid and do "kill -9 <pid>". The real question is can you do the above before you session is killed. When typing something that could cause harm, you can always pause for a moment before hitting enter and make sure that what you are doing is really what you wanted to do.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Init 6 & Init 0 problem

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

different between soft reboot and hard reboot

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

how to stop others users to stop viewing what i am doing ?

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

diff between reboot and init 6 in 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

How to I change init levels after typing init 1

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

Difference between 'init s' and 'init 1'

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

How to stop monitoring of servers at the time of reboot through shell 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

Problem on init 0, execution is the same with init 6

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

What is the diffe b/w init s and init S

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

init-script failing because of /etc/rc.d/init.d/functions

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
kill(2) 							System Calls Manual							   kill(2)

NAME
kill(), raise() - send a signal to a process or a group of processes SYNOPSIS
DESCRIPTION
The system call sends a signal to a process or a group of processes, as specified by pid. The signal to be sent is specified by sig and is either one from the list given in or The system call sends a signal to the executing process or thread. The signal to be sent is specified by sig and is either one from the list given in or In a single-threaded process the effect of the function is equivalent to calling When used in a multithreaded program, the function sends the signal specified by sig to the executing thread. The effect of the function is equivalent to calling If sig is (the null signal), error checking is performed but no signal is actually sent. This can be used to check the validity of pid. The real or effective user ID of the sending process must match the real or saved user ID of the receiving process unless the sending process has appropriate privileges. As a single special case, the continue signal can be sent to any process that is a member of the same session as the sending process. The value is defined in the file and is guaranteed not to be the ID of any process in the system or the negation of the ID of any process in the system. If pid is greater than zero and not equal to sig is sent to the process whose process ID is equal to pid. pid can equal unless sig is or If pid is sig is sent to all processes excluding special system processes whose process group ID is equal to the process group ID of the sender. If pid is and the sending process does not have the appropriate privileges, sig is sent to all processes excluding special system processes whose real or saved user ID is equal to the real or effective user ID of the sender. If pid is and the effective user ID of the sender is a user who has appropriate privileges, sig is sent to all processes excluding special system processes. If pid is behaves much as when pid is equal to except that sig is not sent to the calling process. If pid is negative but not or sig is sent to all processes (excluding special system processes) whose process group ID is equal to the absolute value of pid, and whose real and/or effective user ID meets the constraints described above for matching user IDs. Security Restrictions Some or all of the actions associated with this system call are subject to compartmental restrictions. See compartments(5) for more infor- mation about compartmentalization on systems that support that feature. Compartmental restrictions can be overridden if the process pos- sesses the privilege (COMMALLOWED). Processes owned by the superuser may not have this privilege. Processes owned by any user may have this privilege, depending on system configuration. Some or all of the actions associated with this system call require the (OWNER) and/or the (REBOOT) privileges. Processes owned by the superuser will have these privileges. Processes owned by other users may have privilege(s), depending on system configuration. See privi- leges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
Upon successful completion, a value of is returned. Otherwise, a value of is returned and is set to indicate the error. ERRORS
If fails, no signal is sent. is set to one of the following values. sig is neither a valid signal number nor zero. sig is or and pid is that of the initialization process (also known as The user ID of the sending process is not a user who has appropriate privileges and its real or effective user ID does not match the real or saved user ID of the receiving process. The sending and receiving processes are not in the same session and the real or effective user ID does not match the real or saved user ID of the receiving process. No process or process group can be found corresponding to that specified by pid. If fails, no signal is sent. is set to the following value. sig is neither a valid signal number nor zero. APPLICATION USAGE
Threads Considerations can be used to post signals to another process but cannot be used to post signals to a specific thread in another process. For information on posting signals to specific threads within the same process, see pthread_kill(3T). LWP (Lightweight Processes) Considerations Signals cannot be posted to specific LWPs in another process. AUTHOR
was developed by HP, AT&T, and the University of California, Berkeley. SEE ALSO
kill(1), getpid(2), setsid(2), signal(2), sigqueue(2), pthread_kill(3T). STANDARDS CONFORMANCE
kill(2)
All times are GMT -4. The time now is 01:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy