Exit script when shutdown or reboot command is given
This is probably a simple question, but I'm new with writing scripts for Linux (IPFire in this case) and Google wasn't helpful with this.
When creating a script, what is the best and/or proper way to have it exit automatically if the reboot or shutdown command is given? If that's even necessary, I don't know if Linux kills everything that's running by itself or waits like Windows for user input to kill something that was still running.
Anyway, the only thing I could come up with was
The idea is that the script stays in the while-loop while runlevel is 3, as in normal operation. When the shutdown or reboot command is given, runlevel changes to either 0 or 6, as in not 3, meaning the while-loop will exit. Well, that's the idea anyway.
Does anyone have any thoughts or comments on this?
Hi, i have sco openserver 5.0.6 but have a problem with shutdown or reboot commands.
The string I use is "shutdown -g0 -y" but the system just hangs on "The sytem is down" . I used to get a "Safe to turn of" but now nothing. Same with "reboot" the sytem just freezes.
Any suggestions? (1 Reply)
Dear all,
I want to control my server from shutting down and rebooting.
It will ask for some question before the process, ex: who are you? what is the reason for shutting down? ...
I think I can overide that binary of shutdown/reboot command, but it is confused.
We have many way to... (5 Replies)
Hi,
How can I call my shell script, when I execute 'exit' command?
For eg. I am logging out the root login by 'exit' command. My script 'colinfo' shold execute before logging out. I don't want to use any wrapper script. (2 Replies)
Hi,
please could someone advise the best command to shutdown and then for it to reboot back online again.
Note: I shall be doing this from a telent session.
regards
venhart (3 Replies)
PROBLEM:
I need to ssh into multiple remote machines, send a shutdown command and exit. The remote servers will then run their own scripts to gracefully shutdown their applications before shutting down.
ONE: This is to be achieved without using public key authentication; this is being avoided... (2 Replies)
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)
Hi,
I'm using 2.6.11 kernel on ARM 9. Below are the messages I get issuing different commands.
When I give "reboot" I get run level 6 initiated and get the following messages. I have nothing to complaint about it. All the scripts in rc6.d are executed.
The system is going down for reboot... (3 Replies)
Hi all,
I have a shell script inside which i am executing another shell script. In the inner script im executing a command. i want the status of that command in the outer script to perform some validations.
How to get its status please help!!1
Im using ksh. (2 Replies)
Hello,
I have a backup script that runs an rsync backup to an external drive. I use the script frequently on Windows and Linux and have installed it on a Mac. The script has an option to run shutdown after the backup has completed. Since backup can take hours to run, this is an option that is... (10 Replies)
Discussion started by: LMHmedchem
10 Replies
LEARN ABOUT MOJAVE
runlevel
RUNLEVEL(8) runlevel RUNLEVEL(8)NAME
runlevel - Print previous and current SysV runlevel
SYNOPSIS
runlevel [options...]
OVERVIEW
"Runlevels" are an obsolete way to start and stop groups of services used in SysV init. systemd provides a compatibility layer that maps
runlevels to targets, and associated binaries like runlevel. Nevertheless, only one runlevel can be "active" at a given time, while systemd
can activate multiple targets concurrently, so the mapping to runlevels is confusing and only approximate. Runlevels should not be used in
new code, and are mostly useful as a shorthand way to refer the matching systemd targets in kernel boot parameters.
Table 1. Mapping between runlevels and systemd targets
+---------+-------------------+
|Runlevel | Target |
+---------+-------------------+
|0 | poweroff.target |
+---------+-------------------+
|1 | rescue.target |
+---------+-------------------+
|2, 3, 4 | multi-user.target |
+---------+-------------------+
|5 | graphical.target |
+---------+-------------------+
|6 | reboot.target |
+---------+-------------------+
DESCRIPTION
runlevel prints the previous and current SysV runlevel if they are known.
The two runlevel characters are separated by a single space character. If a runlevel cannot be determined, N is printed instead. If neither
can be determined, the word "unknown" is printed.
Unless overridden in the environment, this will check the utmp database for recent runlevel changes.
OPTIONS
The following option is understood:
--help
Print a short help text and exit.
EXIT STATUS
If one or both runlevels could be determined, 0 is returned, a non-zero failure code otherwise.
ENVIRONMENT
$RUNLEVEL
If $RUNLEVEL is set, runlevel will print this value as current runlevel and ignore utmp.
$PREVLEVEL
If $PREVLEVEL is set, runlevel will print this value as previous runlevel and ignore utmp.
FILES
/run/utmp
The utmp database runlevel reads the previous and current runlevel from.
SEE ALSO systemd(1), systemd.target(5), systemctl(1)systemd 237 RUNLEVEL(8)