Sponsored Content
Full Discussion: Linux Changing Run Levels
Operating Systems Linux Debian Linux Changing Run Levels Post 302985680 by hicksd8 on Monday 14th of November 2016 06:39:47 AM
Old 11-14-2016
Were you logged in as root when you ran:

Code:
who -r

? Yes, your posted output of this command looks strange.

Please post the output of:

Code:
# runlevel

What does that say.

I would also add that runlevel 5 in some distributions tells init to shutdown (in an orderly manner) AND power off (if the hardware supports power off).
Runlevel 0 will shutdown and halt the system leaving power on.
This User Gave Thanks to hicksd8 For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Too many levels of symbolic links

Hi, Is there a limit to the number of symbolic links you can have? I tried to vi the symbolic link relating to a file and got the following error: "filename" Too many levels of symbolic links There is only one symbolic link to one file in this case, but there are >2000 other links to... (2 Replies)
Discussion started by: Bab00shka
2 Replies

2. Solaris

RAID Levels

hi, what are the RAID Levels followed for various File systems ? thanks (3 Replies)
Discussion started by: sol8admin
3 Replies

3. Solaris

Init levels

I have a problem, i dont know if its a normal behaviour or not, i can go to a lower init level, but i cant go to a higher one again, for instance i can run the command init 2 while im at init 3 and when i do who -r i find myself go down to 2 but if i type init 3 and wait im still finding myself in... (1 Reply)
Discussion started by: XP_2600
1 Replies

4. UNIX for Advanced & Expert Users

Unix Run Levels confusion

Hi, Could somebody throw some light on the below queries: - For a run-level X, the S* scripts are executed when coming here from X-n run-level. The K* scripts are executed when coming to X runlevel from X+n runlevel. - Does reaching to runlevel X from X-3 executes K* scritps from X-2 & X-1... (4 Replies)
Discussion started by: vibhor_agarwali
4 Replies

5. UNIX for Dummies Questions & Answers

Search through 2 levels of zip

Hi guys, I know I'm missing something simple here. We have about 500 zipped files in a directory which contain more zip files and within those I need to find a file without unzipping everything. I know I can use zipinfo which I'm trying to create a for loop to go through the files and... (4 Replies)
Discussion started by: petef
4 Replies

6. Solaris

Levels of support

Hello, I have a simple question because I can not find the information at oracle.com I want to buy support for OS Solaris and Servers hardware. I need information what are the levels of support and how much they cost? I need a help. Have a nice day (3 Replies)
Discussion started by: bieszczaders
3 Replies

7. Cybersecurity

Unable to run 'su' and 'sudo' after changing permissions on /etc

Hello, I'm running rhel6 64bit. Accidentally I ran % chmod -R 777 /etc and after that I have a problem to do 'su' or 'sudo'. When I did sudo it complained that /etc/sudoers has 777 while it should be 0440. I changed that and also restored right permission for: -rw-r--r-- 1 root root 1966 May 19... (2 Replies)
Discussion started by: susja
2 Replies

8. AIX

AIX How to run a Shell Script by changing the User

Hi All, Currently our application is running on the server having AIX 5.3 OS. What we intend to do is to run a shell script owned by another user and needs to be run as that particular user. I was trying to create a shell script using the su command before running the actual script (which... (4 Replies)
Discussion started by: acoomer
4 Replies

9. Solaris

Run levels in Solaris 11

Hi Guys, I need to change the following script ( which is good for Linux) for Solris 11 #start oracle start on runlevel stop on runlevel What it should be for Solrais 11. Thanks for your help. Regards Terry (2 Replies)
Discussion started by: terrykhatri531
2 Replies
SHUTDOWN(8)						Linux System Administrator's Manual					       SHUTDOWN(8)

NAME
shutdown - bring the system down SYNOPSIS
/sbin/shutdown [-akrhPHfFnc] [-t sec] time [warning message] DESCRIPTION
shutdown brings the system down in a secure way. All logged-in users are notified that the system is going down, and login(1) is blocked. It is possible to shut the system down immediately or after a specified delay. All processes are first notified that the system is going down by the signal SIGTERM. This gives programs like vi(1) the time to save the file being edited, mail and news processing programs a chance to exit cleanly, etc. shutdown does its job by signalling the init process, asking it to change the runlevel. Runlevel 0 is used to halt the system, runlevel 6 is used to reboot the system, and runlevel 1 is used to put to system into a state where administrative tasks can be performed; this is the default if neither the -h or -r flag is given to shutdown. To see which actions are taken on halt or reboot see the appropriate entries for these runlevels in the file /etc/inittab. OPTIONS
-a Use /etc/shutdown.allow. -k Don't really shutdown; only send the warning messages to everybody. -r Reboot after shutdown. -h Halt or power off after shutdown. -P Halt action is to turn off the power. -H Modifier to the -h flag. Halt action is to halt or drop into boot monitor on systems that support it. Must be used with the -h flag. -f Skip fsck on reboot. -F Force fsck on reboot. -n [DEPRECATED] Don't call init(8) to do the shutdown but do it ourself. The use of this option is discouraged, and its results are not always what you'd expect. -c Cancel a waiting shutdown. ("shutdown now" is no longer waiting.) With this option it is of course not possible to give the time argument, but you can enter explanatory message arguments on the command line that will be sent to all users. -t sec Tell init(8) to wait sec seconds between sending processes the warning and the kill signal, before changing to another runlevel. time When to shutdown. warning message Message to send to all users. The time argument can have different formats. First, it can be an absolute time in the format hh:mm, in which hh is the hour (1 or 2 dig- its) and mm is the minute of the hour (in two digits). Second, it can be in the format +m, in which m is the number of minutes to wait. The word now is an alias for +0. If shutdown is called with a delay, it will create the advisory file /etc/nologin which causes programs such as login(1) to not allow new user logins. This file is created five minutes before the shutdown sequence starts. Shutdown removes this file if it is stopped before it can signal init (i.e. it is cancelled or something goes wrong). It also removes it before calling init to change the runlevel. The -f flag means `reboot fast'. This only creates an advisory file /fastboot which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide not to run fsck(1) since the system has been shut down in the proper way. After that, the boot process should remove /fastboot. The -F flag means `force fsck'. This only creates an advisory file /forcefsck which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide to run fsck(1) with a special `force' flag so that even properly unmounted file systems get checked. After that, the boot process should remove /forcefsck. The -n flag causes shutdown not to call init, but to kill all running processes itself. shutdown will then turn off quota, accounting, and swapping and unmount all file systems. ACCESS CONTROL
shutdown can be called from init(8) when the magic keys CTRL-ALT-DEL are pressed, by creating an appropriate entry in /etc/inittab. This means that everyone who has physical access to the console keyboard can shut the system down. To prevent this, shutdown can check to see if an authorized user is logged in on one of the virtual consoles. If shutdown is called with the -a argument (add this to the invocation of shutdown in /etc/inittab), it checks to see if the file /etc/shutdown.allow is present. It then compares the login names in that file with the list of people that are logged in on a virtual console (from /var/run/utmp). Only if one of those authorized users or root is logged in, it will proceed. Otherwise it will write the message shutdown: no authorized users logged in to the (physical) system console. The format of /etc/shutdown.allow is one user name per line. Empty lines and comment lines (prefixed by a #) are allowed. Currently there is a limit of 32 users in this file. Note that if /etc/shutdown.allow is not present, the -a argument is ignored. HALT OR POWEROFF
The -H option just sets the init environment variable INIT_HALT to HALT, and the -P option just sets that variable to POWEROFF. The shut- down script that calls halt(8) as the last thing in the shutdown sequence should check these environment variables and call halt(8) with the right options for these options to actually have any effect. Debian 3.1 (sarge) supports this. FILES
/fastboot /etc/inittab /etc/init.d/halt /etc/init.d/reboot /etc/shutdown.allow NOTES
A lot of users forget to give the time argument and are then puzzled by the error message shutdown produces. The time argument is manda- tory; in 90 percent of all cases this argument will be the word now. Init can only capture CTRL-ALT-DEL and start shutdown in console mode. If the system is running the X window System, the X server pro- cesses all key strokes. Some X11 environments make it possible to capture CTRL-ALT-DEL, but what exactly is done with that event depends on that environment. Shutdown wasn't designed to be run setuid. /etc/shutdown.allow is not used to find out who is executing shutdown, it ONLY checks who is currently logged in on (one of the) console(s). AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl SEE ALSO
fsck(8), init(8), halt(8), poweroff(8), reboot(8) November 12, 2003 SHUTDOWN(8)
All times are GMT -4. The time now is 02:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy