Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support Shutdown to a Halt and restart Post 302443046 by edfair on Friday 6th of August 2010 11:53:48 AM
Old 08-06-2010
See if you can find documentation on init. That should give you several levels of operation you can initiate from your login. Be careful though, you would need to use the same level of access to log in again.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

where's solaris halt log?

hi folks could tell my anyone where solaris 8 stores the logs about shutdown/halt command. I found no entries in syslog, but there more logs directories. probabaly a stupid question, but fast help would be great! thanks king regards, patrick (6 Replies)
Discussion started by: mrsaint
6 Replies

2. Programming

How to halt Prog Execution for some time?

Hi, Perhaps I am asking a silly question, but I really don't know about it. Can anyone tell me the function for "sleep" kind of functionality in C language for Unix. I don't think any function with the name of sleep() exits in Unix's C language. or perhaps I am not known with the header file... (3 Replies)
Discussion started by: Ahsan
3 Replies

3. Solaris

difference b/w halt shutdown

Hi, I want to know the difference between halt and shutdown commands and which is better to use? Regards, visu (2 Replies)
Discussion started by: visu_ak
2 Replies

4. Solaris

Restart/Shutdown the Solaris from SC>

Hi Experts, I am running solris 9. Sun-Fire 880. How do i shutdowon the whole server using ALOM i.e sc> console. If the server is down or somehow hang How do i Restart from sc> //purple (6 Replies)
Discussion started by: thepurple
6 Replies

5. Solaris

unable to halt the zone

Hi Experts, I have to delete the non- global zone from one of the server. As per my understanding we need to halt the zone , then uninstall and later delete it with zoneadm however once I am trying to halt the zone the screen is getting hanged, after canceling the process and... (23 Replies)
Discussion started by: kumarmani
23 Replies

6. UNIX for Dummies Questions & Answers

Script to force Oracle database shutdown when shutdown immediate does not work

I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS). Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies

7. UNIX for Advanced & Expert Users

SCO Open Server 6 - System Halt

========================================================= Errrr previously post: https://www.unix.com/sco/140055-sco-open-server-6-system-halt.html Then I think it's better to post here. If I wrong, please ignore. ========================================================= Dear All, Newbie... (1 Reply)
Discussion started by: virgani
1 Replies

8. Linux

Delay gnome shutdown/restart

Hi to all. My first message here, but i following you via twitter feed from many time... The question: I need to delay 5-10 seconds the shutdown command executed when the user click on the power off/reboot in their session or at login screen. I need that because i have in the background a... (18 Replies)
Discussion started by: mendez
18 Replies

9. Solaris

Solaris paging bringing system to halt

Hi experts, I am running a solaris 10 with oracle 10 on a system with 96 GB physical memory. the system has a lot of swap space. the oracle SGA is 50 GB and PGA 40 GB. Here are the stats vmstat -i interrupt total rate -------------------------------- clock ... (5 Replies)
Discussion started by: afadaghi
5 Replies
init(8) 						      System Manager's Manual							   init(8)

NAME
init - Process control initialization SYNOPSIS
/sbin/init [0123456789MmQqSs] DESCRIPTION
The init program initializes the system by creating and controlling processes. The processes run by init at each run level are defined in the inittab file. The init program reads and processes the entries in the inittab file. The init program considers the system to be in a run level at any given time; each run level has a specific group of processes that run at that level. The init program operates in one of eleven run levels: 0-9 and Ss. Of these, only 0, s, 2, and 3 are configured in the inittab file by default. The run level changes when a privileged user invokes init. The new init sends appropriate signals to the original init that tell it which run level to change to. Running the init program is the last step in the boot process after the root file system is mounted. The init program scans the inittab file and looks for an entry with the initdefault keyword. If the entry is there, init uses the run level specified in that entry as the initial run level to enter. If the entry is not found in the inittab file or if the inittab file does not exist, init requests that the user enter a run level from the system console, /dev/console. If the user enters the letter s, init enters single user state, assigns the virtual console terminal to the user's terminal and opens it for reading and writing. The su command is invoked and the system displays a message on the console stating the location of the virtual console. To change the run level, the user specifies either the 0, 2, 3, or s flag. For the first post-boot execution of init to a run level other than single user, it searches the inittab file for entries at the new run level that have the boot or bootwait keywords. If the run level that is specified matches the entry, the init program acts on these entries before processing other entries in the inittab file. Any special initialization of the system, such as checking and mounting file systems, takes place before users are allowed on the system. The init program then scans the inittab file to find all entries that are to be handled for that level. Before starting a new process, init reads each entry in the inittab file, and for each entry that should be respawned, init forks a child process. After spawning all required processes, init waits for one of its descendant processes to stop, a power-fail signal, or a signal that it should change the run level. If one of the preceding three conditions occurs, init reexamines the inittab file. You can add new entries to the inittab file, but init does not reexamine the file until one of the three previous conditions actually occurs. To immedi- ately reexamine the inittab file, invoke the init program with the q flag. FLAGS
Shuts down and halts the system. Changes the run level to a multiuser state with local processes and daemons. Changes the run level to a multiuser state with remote processes and daemons. Changes run level to that specified by the number flag in the /etc/inittab file. If no such entry exists, no action is taken and no message is output. Moves control to the console device and halts to single-user mode. Forces init to reexamine the entries in the inittab file and terminates any live processes which have had their configuration entries removed from /etc/inittab. Users should be aware that when a getty(8) line has been removed from /etc/inittab, and a login shell is active on the ter- minal line that was formerly designated in inittab as a getty entry, the login shell will be killed. Changes the run level to a single user state with only the essential kernel services. FILES
Specifies the command path Specifies the init command control file Specifies the permanent login accounting file RELATED INFORMATION
Commands: getty(8), rc0(8), rc2(8), rc3(8), shutdown(8) Calls: kill(2), reboot(2) Files: inittab(4) delim off init(8)
All times are GMT -4. The time now is 05:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy