SlideShare a Scribd company logo
Junior Level Linux Certification
Exam Objectives
Key Knowledge Areas
Set the default runlevel.
Change between run levels including single user mode.
Shutdown and reboot from the command line.
Alert users before switching runlevels or other major system event.
Properly terminate processes.
Objective 1: System Architecture
Change runlevels and shutdown or reboot system Weight: 3
Terms and Utilities
/etc/inittab
shutdown
init
/etc/init.d
telinit
2
Runlevels , shutdown, and reboot
Runlevels
3
Runlevels define what tasks are accomplished in the current state (runlevel) of a Linux
system.
Every Linux system supports 3 basic runlevels, plus 1 or more runlevels for normal operation.
Basic Linux runlevels
Level Purpose
0 Shut down (or halt) the system
1 Single-user mode; usually aliased as s or S
6 Reboot the system
Common Linux runlevels
Level Purpose
2 Multiuser mode without networking
3 Multiuser mode with networking
5 Multiuser mode with networking and the X Window System
- Slackware uses runlevel 4 for full system running X Window system.
- Debian and Ubuntu, use a single runlevel for any multiuser mode, (runlevel 2)
consult documentation for the distribution
Runlevels , shutdown, and reboot
Default runlevel
4
When system starts, default runlevel is determined from id: entry in /etc/inittab.
Ex:
yourname@yourcomp~> grep "^id:" /etc/inittab
id:5:initdefault:
Entry for Fedora 8 or openSUSE 11.2, with runlevel 5 for the X Window System.
Runlevels , shutdown, and reboot
Changing runlevels
5
To make a permanent change in runlevel,
•edit /etc/inittab and change the default level
To make one boot in other runlevel
(exemple: to edit the Linux System, or to install or build kernel modules).
•At boot time by editing the kernel cmdline in GRUB or add a parameter to LILO;
•Use a single digit to specify desired runlevel.
each runlevel corresponds to scripts /etc/rc.d/rc?.d/S* (? for number 0 to 6).
When there’s change in runlevel, init runs a script which stops all extra processes in the
current runlevel, and starts required processes from the new runlevel
Runlevels , shutdown, and reboot
Changing runlevels
6
Ex 1: Changin runlevels at boot time - enter ‘e’ command to edit.
Runlevels , shutdown, and reboot
Changing runlevels
7
Ex 2: In menu with root, kernel, initrd - select kernel and press 'e' to edit
Runlevels , shutdown, and reboot
Changing runlevels
8
Ex 3:
In end of line - add space and digit runlevel '3'.
Remove 'quiet' if you wish, or modify any other parameters if needed
Runlevels , shutdown, and reboot
Changing runlevels
9
To change runlevel without rebooting the system. The command used is telinit.
Use 1st
the command runlevel to show previous runlevel and current one.
If first output is 'N': the runlevel has not been changed since boot.
Ex: yourname@yourcomp~> runlevel
N 3
yourname@yourcomp~> telinit 4
Confirm the new runlevel after the change. Again with runlevel command
Ex: yourname@yourcomp~> runlevel
3 4
Runlevels , shutdown, and reboot
telinit and init
10
telinit is a symbolic link to init
Since init runs as PID 1 at boot time the init executables know if the command invoked on
prompt is the init or telinit and behaves accordingly.
As a symbolic link:
you may use init5 instead of telinit5 to switch to runlevel 5 or any other.
Ex: yourname@yourcomp~> ls -l $(which telinit)
lrwxrwxrwx 1 root root 4 2008-04-01 07:50 /sbin/telinit -> init
Runlevels , shutdown, and reboot
Single-user mode
11
Single-user mode (runlevel 1)is selected to:
Recover a filesystem or database, or install and test new hardware.
System environment:
•shell with a minimal system;
•Usually without networking;
•Without daemons running (or very few);
•Goes straight into a shell prompt as root, or must log with authentication.
Ex: yourname@yourcomp~> telinit 1
yourname@yourcomp~> telinit S
Remember:
telinit 1 or init switch to Single-user mode for admin will stop multiuser activity.
Its a abrupt process - can cause users to lose work and processes to terminate abnormally.
Runlevels , shutdown, and reboot
Clean shutdown
12
Preferred method to shut down or reboot the system is the shutdown command
Process:
1.Sends warning message to all logged-in users and blocks any further logins.
2.Signals init to switch runlevels.
3. init process then sends all running processes a SIGTERM signal, giving them chance to save data and
terminate properly.
4.After 5 sec, or another delay specified, init sends a SIGKILL signal to forcibly end each remaining process.
By default, shutdown switches to runlevel 1 (single-user mode).
Specify -h option to halt system, -r option to reboot.
Standard message is issued in addition to any message you specify
Shutdown time may be:
Absolute in hh:mm format, Relative time in n (n=number minutes until shutdown) +0= Now
Cancel delayed shutdown: press Ctrl-c or command shutdown -c.
Runlevels , shutdown, and reboot
Clean shutdown
13
Ex: yourname@yourcomp~# shutdown 5 File system recovery needed
Broadcast message from root (pts/1) (Tue Jan 4 08:05:24 2011):
File system recovery needed
The system is going DOWN to maintenance mode in 5 minutes!
^C
Shutdown cancelled.
yourname@yourcomp~# shutdown -r 10 Reloading updated kernel&
[1] 18784
[yourname@yourcomp~#
Broadcast message from root (pts/1) (Tue Jan 4 08:05:53 2011):
Reloading updated kernel
The system is going DOWN for reboot in 10 minutes!
yourname@yourcomp~# fg
shutdown -r 10 Reloading updated kernel
^C
Shutdown cancelled.
yourname@yourcomp~# shutdown -h 23:59&
[1] 18788
[root@pinguino ~]# shutdown –c
Shutdown cancelled.
[1]+ Done shutdown -h 23:59
Runlevels , shutdown, and reboot
Clean shutdown
14
Ex:
If time till shutdown exceeds 15 min., message is not sent until 15 minutes before the event.
yourname@yourcomp~# date;shutdown -t60 17 Time to do backups&
Tue Jan 4 08:12:55 EST 2011
[1] 18825
yourname@yourcomp~# date
Tue Jan 4 08:14:13 EST 2011
yourname@yourcomp~#
Broadcast message from root (pts/1) (Tue Jan 4 08:14:55 2011):
Time to do backups
The system is going DOWN to maintenance mode in 15 minutes!
If shutdown is canceled, use wall command to send a warning to all users alerting them
that the system is not going down.
Runlevels , shutdown, and reboot
Halt, reboot, and poweroff
15
halt command: halts the system
If any of these 3 commands are called when system is not in runlevel 0 or 6,
then the corresponding shutdown command will be invoked instead.
poweroff command: Is a symbolic link to halt command,
which halts the system and attempts to power it off.
reboot command: Is a symbolic link to halt command,
which halts the system and then reboots it.
Runlevels , shutdown, and reboot
inittab
16
When /sbin/init is started by kernel, it reads /etc/inittab for the startup sequence.
The lines in /etc/inittab determine the startup behaviour of your system.
Common inittab Actions
Respawn Restart process whenever it terminates. Usually used for getty processes, that monitors logins.
Wait Start process once when specified runlevel is entered and wait for its termination before init proceeds.
once Start the process once when the specified runlevel is entered.
Initdefault Specifies the runlevel to enter after system boot.
ctrlaltdel Execute associated process when init receives the SIGINT signal.
example: when someone on the system console presses CTRL-ALT-DEL.
Common initab Format [id:runlevels:action:process]
Id: unique identifier of one to four characters. Older versions limited to two characters.
runlevels: lists runlevels for which action for this id should be taken. If no runlevels are listed, do action for
all runlevels.
action: describes which of several possible actions should be taken.
process tells which process, if any, should be run when action on this line is performed.
Runlevels , shutdown, and reboot
inittab
17
Ex:
Part 1
##
inittab This file describes how the INIT process should set up
# the system in a certain run-level.
##
Author: Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes
#
# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:5:initdefault:
Before thinking runlevels, init runs the sysinit script.
# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit
Runlevels , shutdown, and reboot
inittab
18
Ex:
Part 2 l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6
For actual runlevel chosen (before in id:5:initdefault), a script is run – in this case /etc/rc.d/rc 5.
Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
Trapping Ctrl-Alt-Delete for keyboard system reboot.
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
# Run xdm in runlevel 5
x:5:respawn:/etc/X11/prefdm -nodaemon
In runlevel 2 ,3 , 4, 5, init verifies if the /etc/inittab as the following programs running:
(mingetty handles terminal login, and mgetty handles modem dialin access)
Runlevels , shutdown, and reboot
inittab
19
Ex:
Part 3 # When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
Power failure settings.
Runlevels , shutdown, and reboot
Initialization scripts
20
Scripts used by init for:
starting the system; shutting down; changing runlevels
are typically in /etc/init.d or /etc/rc.d directory.
There’s a series of symbolic links in rcn.d directories. One directory for each runlevel n,
They control if the script is started and stopped when entering a runlevel.
/etc/rc.d/rc 0
/etc/rc.d/rc 1
/etc/rc.d/rc 2
/etc/rc.d/rc 3
/etc/rc.d/rc 4
/etc/rc.d/rc 5
/etc/rc.d/rc 6
man init and man inittab
Runlevels , shutdown, and reboot
Init scripts
21
Ex: yourname@yourcomp~# find /etc -path "*rc[0-9]*.d/???au*"
/etc/rc.d/rc2.d/S27auditd
/etc/rc.d/rc2.d/K72autofs
/etc/rc.d/rc4.d/S27auditd
/etc/rc.d/rc4.d/S28autofs
/etc/rc.d/rc5.d/S27auditd
/etc/rc.d/rc5.d/S28autofs
/etc/rc.d/rc0.d/K72autofs
/etc/rc.d/rc0.d/K73auditd
/etc/rc.d/rc6.d/K72autofs
/etc/rc.d/rc6.d/K73auditd
/etc/rc.d/rc1.d/K72autofs
/etc/rc.d/rc1.d/K73auditd
/etc/rc.d/rc3.d/S27auditd
/etc/rc.d/rc3.d/S28autofs
yourname@yourcomp~# cd /etc/rc.d/rc5.d
yourname@yourcomp rc5.d# ls -l ???a*
lrwxrwxrwx 1 root root 16 2008-04-07 11:29 S27auditd -> ../init.d/auditd
lrwxrwxrwx 1 root root 16 2008-04-01 07:51 S28autofs -> ../init.d/autofs
lrwxrwxrwx 1 root root 15 2008-04-01 14:03 S44acpid -> ../init.d/acpid
lrwxrwxrwx 1 root root 13 2008-04-01 07:50 S95atd -> ../init.d/atd
lrwxrwxrwx 1 root root 22 2008-04-01 07:54 S96avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 17 2008-11-17 13:40 S99anacron -> ../init.d/anacron
The links have: K (stopped) or S (Started); two-digit number (priority), name of service
Here audit and autofs services have Knn entries in all runlevels and Snn entries for runlevels 3 and 5.
S indicates that the service is started when that runlevel is entered, K indicates that it should be stopped.
nn component of link name indicates priority order in which the service should be started or stopped.
In example, audit is started before autofs, and it is stopped later.
Runlevels , shutdown, and reboot
Init vs. Upstart
22
Traditional method of booting a Linux system is based on UNIX System V init process.
For systems where everything is known and connected when the system starts it works well
1st
Involves loading initial RAM disk (initrd)
2nd
passing control to a program called init (init program is installed as part of sysvinit package)
3rd
init program runs a series of scripts in a predefined order to bring up the system.
If something that is expected is not available, the init process typically waits for it.
Modern systems with hot-pluggable devices, network file systems, present new challenges.
waiting for hardware that may come available later, is not desirable.
An alternative initialization process was first introduced in Ubuntu 6.10 ("Edgy Eft") in 2006.
It’s called upstart
Has supplanted the init process in Ubuntu, Fedora, and others, with vestiges of init remaining and still in use
http://upstart.ubuntu.com/
Runlevels , shutdown, and reboot
Upstart
23
In contrast to the static init scripts the upstart system is driven by events.
Events triggered by hardware changes, started or stoped tasks, by processes on the system.
Example:
connecting a USB drive might cause udev service to send a block-device-added event,
which would cause a defined task to check /etc/fstab and mount the drive.
upstart initialization program replaces /sbin/init.
•Upstart jobs are defined in /etc/init directory and subdirectories.
•upstart system will process /etc/inittab and System V init scripts.
New Fedora /etc/inittab contains only id entry for initdefault;
New Ubuntu does not have /etc/inittab (must create one to specify a default runlevel).
Events used to trigger tasks or services (known as jobs).
Runlevels , shutdown, and reboot
Upstart
24
Upstart has command initctl
Gives interaction with upstart init daemon.
(start or stop jobs, list jobs, get status of jobs, emit events, restart init process)
Ex: yourname@yourcomp~# initctl list
rc stop/waiting
tty (/dev/tty3) start/running, process 1486
tty (/dev/tty2) start/running, process 1484
tty (/dev/tty6) start/running, process 1492
tty (/dev/tty5) start/running, process 1490
tty (/dev/tty4) start/running, process 1488
plymouth-shutdown stop/waiting
control-alt-delete stop/waiting
system-setup-keyboard start/running, process 1000
readahead-collector stop/waiting
vpnc-cleanup stop/waiting
quit-plymouth stop/waiting
rcS stop/waiting
prefdm start/running, process 1479
init-system-dbus stop/waiting
ck-log-system-restart stop/waiting
readahead stop/waiting
ck-log-system-start stop/waiting
start-ttys stop/waiting
readahead-disable-services stop/waiting
ck-log-system-stop stop/waiting
rcS-sulogin stop/waiting
serial stop/waiting
Fim de sessão
25

More Related Content

PPT
101 4.2 maintain the integrity of filesystems
PPT
101 3.5 create, monitor and kill processes
PPT
101 3.2 process text streams using filters
PPT
101 3.4 use streams, pipes and redirects
DOCX
Perf stat windows
DOCX
Tier 2 net app baseline design standard revised nov 2011
PDF
Linux Security Quick Reference Guide
PDF
LINUX System Call Quick Reference
101 4.2 maintain the integrity of filesystems
101 3.5 create, monitor and kill processes
101 3.2 process text streams using filters
101 3.4 use streams, pipes and redirects
Perf stat windows
Tier 2 net app baseline design standard revised nov 2011
Linux Security Quick Reference Guide
LINUX System Call Quick Reference

What's hot (20)

PPT
Linux commands
DOCX
Unix system calls
PDF
Linux System Monitoring basic commands
PDF
Useful Linux and Unix commands handbook
PDF
Module 13 - Troubleshooting
PDF
50 most frequently used unix linux commands (with examples)
PDF
VTU 3RD SEM UNIX AND SHELL PROGRAMMING SOLVED PAPERS
PPT
Unix(introduction)
PDF
Programming Embedded linux
PPT
Linux
DOCX
50 Most Frequently Used UNIX Linux Commands -hmftj
PPT
Linux Commands
PPTX
How To Add System Call In Ubuntu OS
DOCX
50 most frequently used unix
PPT
Ch14 system administration
PPT
Linux monitoring and Troubleshooting for DBA's
PDF
Slide lpi mudancas lpic1
PPTX
Linux Process & CF scheduling
Linux commands
Unix system calls
Linux System Monitoring basic commands
Useful Linux and Unix commands handbook
Module 13 - Troubleshooting
50 most frequently used unix linux commands (with examples)
VTU 3RD SEM UNIX AND SHELL PROGRAMMING SOLVED PAPERS
Unix(introduction)
Programming Embedded linux
Linux
50 Most Frequently Used UNIX Linux Commands -hmftj
Linux Commands
How To Add System Call In Ubuntu OS
50 most frequently used unix
Ch14 system administration
Linux monitoring and Troubleshooting for DBA's
Slide lpi mudancas lpic1
Linux Process & CF scheduling
Ad

Viewers also liked (13)

PPT
101 4.6 create and change hard and symbolic links
PPT
101 2.3 manage shared libraries
PPT
101 4.7 find system files and place files in the correct location
PPT
101 1.2 boot the system
PPT
Lpi lição 01 exam 102 objectives
PPT
101 1.1 hardware settings
PPT
Apend. networking generic a
PPT
Lpi lição 01 exam 101 objectives
PPTX
Licão 03 vi editor
PDF
Gnu study guide linux admin 1 (lab work lpi 101) v 0.2
PDF
Lpi 101 study_guide
PDF
Lpi Part 1 Linux Fundamentals
PDF
Linux Network Administration (LPI-1,LPI-2)
101 4.6 create and change hard and symbolic links
101 2.3 manage shared libraries
101 4.7 find system files and place files in the correct location
101 1.2 boot the system
Lpi lição 01 exam 102 objectives
101 1.1 hardware settings
Apend. networking generic a
Lpi lição 01 exam 101 objectives
Licão 03 vi editor
Gnu study guide linux admin 1 (lab work lpi 101) v 0.2
Lpi 101 study_guide
Lpi Part 1 Linux Fundamentals
Linux Network Administration (LPI-1,LPI-2)
Ad

Similar to 101 1.3 runlevels , shutdown, and reboot (20)

PPT
1.3 runlevels, shutdown, and reboot v3
PPT
101 1.3 runlevels , shutdown, and reboot
PPT
101 1.3 runlevels, shutdown, and reboot v2
PDF
Linux : Booting and runlevels
PPTX
Linux startup
DOCX
6 stages of linux boot process
DOCX
6 stages of linux boot process
PPTX
2- System Initialization in Red Hat
DOCX
6 stages of linux boot process
DOC
6 stages of linux boot process
PPT
Linux Booting Process
PDF
01 boot process
ODP
Grub and dracut ii
PDF
Linux boot process
PPT
Unix Administration 2
PDF
Linux fundamental - Chap 11 boot
PPT
Linux booting procedure
PDF
Linux boot process – explained
PDF
Linux booting procedure
PPTX
Linux booting Process
1.3 runlevels, shutdown, and reboot v3
101 1.3 runlevels , shutdown, and reboot
101 1.3 runlevels, shutdown, and reboot v2
Linux : Booting and runlevels
Linux startup
6 stages of linux boot process
6 stages of linux boot process
2- System Initialization in Red Hat
6 stages of linux boot process
6 stages of linux boot process
Linux Booting Process
01 boot process
Grub and dracut ii
Linux boot process
Unix Administration 2
Linux fundamental - Chap 11 boot
Linux booting procedure
Linux boot process – explained
Linux booting procedure
Linux booting Process

More from Acácio Oliveira (20)

PPTX
Security+ Lesson 01 Topic 24 - Vulnerability Scanning vs Pen Testing.pptx
PPTX
Security+ Lesson 01 Topic 25 - Application Security Controls and Techniques.pptx
PPTX
Security+ Lesson 01 Topic 21 - Types of Application Attacks.pptx
PPTX
Security+ Lesson 01 Topic 19 - Summary of Social Engineering Attacks.pptx
PPTX
Security+ Lesson 01 Topic 23 - Overview of Security Assessment Tools.pptx
PPTX
Security+ Lesson 01 Topic 20 - Summary of Wireless Attacks.pptx
PPTX
Security+ Lesson 01 Topic 22 - Security Enhancement Techniques.pptx
PPTX
Security+ Lesson 01 Topic 15 - Risk Management Best Practices.pptx
PPTX
Security+ Lesson 01 Topic 13 - Physical Security and Environmental Controls.pptx
PPTX
Security+ Lesson 01 Topic 14 - Disaster Recovery Concepts.pptx
PPTX
Security+ Lesson 01 Topic 06 - Wireless Security Considerations.pptx
PPTX
Security+ Lesson 01 Topic 04 - Secure Network Design Elements and Components....
PPTX
Security+ Lesson 01 Topic 02 - Secure Network Administration Concepts.pptx
PPTX
Security+ Lesson 01 Topic 01 - Intro to Network Devices.pptx
PPTX
Security+ Lesson 01 Topic 08 - Integrating Data and Systems with Third Partie...
PPTX
Security+ Lesson 01 Topic 07 - Risk Related Concepts.pptx
PPTX
Security+ Lesson 01 Topic 05 - Common Network Protocols.pptx
PPTX
Security+ Lesson 01 Topic 11 - Incident Response Concepts.pptx
PPTX
Security+ Lesson 01 Topic 12 - Security Related Awareness and Training.pptx
PPTX
Security+ Lesson 01 Topic 17 - Types of Malware.pptx
Security+ Lesson 01 Topic 24 - Vulnerability Scanning vs Pen Testing.pptx
Security+ Lesson 01 Topic 25 - Application Security Controls and Techniques.pptx
Security+ Lesson 01 Topic 21 - Types of Application Attacks.pptx
Security+ Lesson 01 Topic 19 - Summary of Social Engineering Attacks.pptx
Security+ Lesson 01 Topic 23 - Overview of Security Assessment Tools.pptx
Security+ Lesson 01 Topic 20 - Summary of Wireless Attacks.pptx
Security+ Lesson 01 Topic 22 - Security Enhancement Techniques.pptx
Security+ Lesson 01 Topic 15 - Risk Management Best Practices.pptx
Security+ Lesson 01 Topic 13 - Physical Security and Environmental Controls.pptx
Security+ Lesson 01 Topic 14 - Disaster Recovery Concepts.pptx
Security+ Lesson 01 Topic 06 - Wireless Security Considerations.pptx
Security+ Lesson 01 Topic 04 - Secure Network Design Elements and Components....
Security+ Lesson 01 Topic 02 - Secure Network Administration Concepts.pptx
Security+ Lesson 01 Topic 01 - Intro to Network Devices.pptx
Security+ Lesson 01 Topic 08 - Integrating Data and Systems with Third Partie...
Security+ Lesson 01 Topic 07 - Risk Related Concepts.pptx
Security+ Lesson 01 Topic 05 - Common Network Protocols.pptx
Security+ Lesson 01 Topic 11 - Incident Response Concepts.pptx
Security+ Lesson 01 Topic 12 - Security Related Awareness and Training.pptx
Security+ Lesson 01 Topic 17 - Types of Malware.pptx

Recently uploaded (20)

PDF
WOOl fibre morphology and structure.pdf for textiles
PDF
Encapsulation theory and applications.pdf
PPTX
OMC Textile Division Presentation 2021.pptx
PPTX
cloud_computing_Infrastucture_as_cloud_p
PDF
NewMind AI Weekly Chronicles - August'25-Week II
PDF
Microsoft Solutions Partner Drive Digital Transformation with D365.pdf
PDF
Hybrid model detection and classification of lung cancer
PPTX
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
PDF
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
PPTX
Chapter 5: Probability Theory and Statistics
PPTX
Tartificialntelligence_presentation.pptx
PDF
Agricultural_Statistics_at_a_Glance_2022_0.pdf
PPTX
TLE Review Electricity (Electricity).pptx
PDF
A comparative analysis of optical character recognition models for extracting...
PDF
Accuracy of neural networks in brain wave diagnosis of schizophrenia
PDF
ENT215_Completing-a-large-scale-migration-and-modernization-with-AWS.pdf
PDF
DASA ADMISSION 2024_FirstRound_FirstRank_LastRank.pdf
PDF
Building Integrated photovoltaic BIPV_UPV.pdf
PPTX
Digital-Transformation-Roadmap-for-Companies.pptx
PDF
Mushroom cultivation and it's methods.pdf
WOOl fibre morphology and structure.pdf for textiles
Encapsulation theory and applications.pdf
OMC Textile Division Presentation 2021.pptx
cloud_computing_Infrastucture_as_cloud_p
NewMind AI Weekly Chronicles - August'25-Week II
Microsoft Solutions Partner Drive Digital Transformation with D365.pdf
Hybrid model detection and classification of lung cancer
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
Chapter 5: Probability Theory and Statistics
Tartificialntelligence_presentation.pptx
Agricultural_Statistics_at_a_Glance_2022_0.pdf
TLE Review Electricity (Electricity).pptx
A comparative analysis of optical character recognition models for extracting...
Accuracy of neural networks in brain wave diagnosis of schizophrenia
ENT215_Completing-a-large-scale-migration-and-modernization-with-AWS.pdf
DASA ADMISSION 2024_FirstRound_FirstRank_LastRank.pdf
Building Integrated photovoltaic BIPV_UPV.pdf
Digital-Transformation-Roadmap-for-Companies.pptx
Mushroom cultivation and it's methods.pdf

101 1.3 runlevels , shutdown, and reboot

  • 1. Junior Level Linux Certification
  • 2. Exam Objectives Key Knowledge Areas Set the default runlevel. Change between run levels including single user mode. Shutdown and reboot from the command line. Alert users before switching runlevels or other major system event. Properly terminate processes. Objective 1: System Architecture Change runlevels and shutdown or reboot system Weight: 3 Terms and Utilities /etc/inittab shutdown init /etc/init.d telinit 2
  • 3. Runlevels , shutdown, and reboot Runlevels 3 Runlevels define what tasks are accomplished in the current state (runlevel) of a Linux system. Every Linux system supports 3 basic runlevels, plus 1 or more runlevels for normal operation. Basic Linux runlevels Level Purpose 0 Shut down (or halt) the system 1 Single-user mode; usually aliased as s or S 6 Reboot the system Common Linux runlevels Level Purpose 2 Multiuser mode without networking 3 Multiuser mode with networking 5 Multiuser mode with networking and the X Window System - Slackware uses runlevel 4 for full system running X Window system. - Debian and Ubuntu, use a single runlevel for any multiuser mode, (runlevel 2) consult documentation for the distribution
  • 4. Runlevels , shutdown, and reboot Default runlevel 4 When system starts, default runlevel is determined from id: entry in /etc/inittab. Ex: yourname@yourcomp~> grep "^id:" /etc/inittab id:5:initdefault: Entry for Fedora 8 or openSUSE 11.2, with runlevel 5 for the X Window System.
  • 5. Runlevels , shutdown, and reboot Changing runlevels 5 To make a permanent change in runlevel, •edit /etc/inittab and change the default level To make one boot in other runlevel (exemple: to edit the Linux System, or to install or build kernel modules). •At boot time by editing the kernel cmdline in GRUB or add a parameter to LILO; •Use a single digit to specify desired runlevel. each runlevel corresponds to scripts /etc/rc.d/rc?.d/S* (? for number 0 to 6). When there’s change in runlevel, init runs a script which stops all extra processes in the current runlevel, and starts required processes from the new runlevel
  • 6. Runlevels , shutdown, and reboot Changing runlevels 6 Ex 1: Changin runlevels at boot time - enter ‘e’ command to edit.
  • 7. Runlevels , shutdown, and reboot Changing runlevels 7 Ex 2: In menu with root, kernel, initrd - select kernel and press 'e' to edit
  • 8. Runlevels , shutdown, and reboot Changing runlevels 8 Ex 3: In end of line - add space and digit runlevel '3'. Remove 'quiet' if you wish, or modify any other parameters if needed
  • 9. Runlevels , shutdown, and reboot Changing runlevels 9 To change runlevel without rebooting the system. The command used is telinit. Use 1st the command runlevel to show previous runlevel and current one. If first output is 'N': the runlevel has not been changed since boot. Ex: yourname@yourcomp~> runlevel N 3 yourname@yourcomp~> telinit 4 Confirm the new runlevel after the change. Again with runlevel command Ex: yourname@yourcomp~> runlevel 3 4
  • 10. Runlevels , shutdown, and reboot telinit and init 10 telinit is a symbolic link to init Since init runs as PID 1 at boot time the init executables know if the command invoked on prompt is the init or telinit and behaves accordingly. As a symbolic link: you may use init5 instead of telinit5 to switch to runlevel 5 or any other. Ex: yourname@yourcomp~> ls -l $(which telinit) lrwxrwxrwx 1 root root 4 2008-04-01 07:50 /sbin/telinit -> init
  • 11. Runlevels , shutdown, and reboot Single-user mode 11 Single-user mode (runlevel 1)is selected to: Recover a filesystem or database, or install and test new hardware. System environment: •shell with a minimal system; •Usually without networking; •Without daemons running (or very few); •Goes straight into a shell prompt as root, or must log with authentication. Ex: yourname@yourcomp~> telinit 1 yourname@yourcomp~> telinit S Remember: telinit 1 or init switch to Single-user mode for admin will stop multiuser activity. Its a abrupt process - can cause users to lose work and processes to terminate abnormally.
  • 12. Runlevels , shutdown, and reboot Clean shutdown 12 Preferred method to shut down or reboot the system is the shutdown command Process: 1.Sends warning message to all logged-in users and blocks any further logins. 2.Signals init to switch runlevels. 3. init process then sends all running processes a SIGTERM signal, giving them chance to save data and terminate properly. 4.After 5 sec, or another delay specified, init sends a SIGKILL signal to forcibly end each remaining process. By default, shutdown switches to runlevel 1 (single-user mode). Specify -h option to halt system, -r option to reboot. Standard message is issued in addition to any message you specify Shutdown time may be: Absolute in hh:mm format, Relative time in n (n=number minutes until shutdown) +0= Now Cancel delayed shutdown: press Ctrl-c or command shutdown -c.
  • 13. Runlevels , shutdown, and reboot Clean shutdown 13 Ex: yourname@yourcomp~# shutdown 5 File system recovery needed Broadcast message from root (pts/1) (Tue Jan 4 08:05:24 2011): File system recovery needed The system is going DOWN to maintenance mode in 5 minutes! ^C Shutdown cancelled. yourname@yourcomp~# shutdown -r 10 Reloading updated kernel& [1] 18784 [yourname@yourcomp~# Broadcast message from root (pts/1) (Tue Jan 4 08:05:53 2011): Reloading updated kernel The system is going DOWN for reboot in 10 minutes! yourname@yourcomp~# fg shutdown -r 10 Reloading updated kernel ^C Shutdown cancelled. yourname@yourcomp~# shutdown -h 23:59& [1] 18788 [root@pinguino ~]# shutdown –c Shutdown cancelled. [1]+ Done shutdown -h 23:59
  • 14. Runlevels , shutdown, and reboot Clean shutdown 14 Ex: If time till shutdown exceeds 15 min., message is not sent until 15 minutes before the event. yourname@yourcomp~# date;shutdown -t60 17 Time to do backups& Tue Jan 4 08:12:55 EST 2011 [1] 18825 yourname@yourcomp~# date Tue Jan 4 08:14:13 EST 2011 yourname@yourcomp~# Broadcast message from root (pts/1) (Tue Jan 4 08:14:55 2011): Time to do backups The system is going DOWN to maintenance mode in 15 minutes! If shutdown is canceled, use wall command to send a warning to all users alerting them that the system is not going down.
  • 15. Runlevels , shutdown, and reboot Halt, reboot, and poweroff 15 halt command: halts the system If any of these 3 commands are called when system is not in runlevel 0 or 6, then the corresponding shutdown command will be invoked instead. poweroff command: Is a symbolic link to halt command, which halts the system and attempts to power it off. reboot command: Is a symbolic link to halt command, which halts the system and then reboots it.
  • 16. Runlevels , shutdown, and reboot inittab 16 When /sbin/init is started by kernel, it reads /etc/inittab for the startup sequence. The lines in /etc/inittab determine the startup behaviour of your system. Common inittab Actions Respawn Restart process whenever it terminates. Usually used for getty processes, that monitors logins. Wait Start process once when specified runlevel is entered and wait for its termination before init proceeds. once Start the process once when the specified runlevel is entered. Initdefault Specifies the runlevel to enter after system boot. ctrlaltdel Execute associated process when init receives the SIGINT signal. example: when someone on the system console presses CTRL-ALT-DEL. Common initab Format [id:runlevels:action:process] Id: unique identifier of one to four characters. Older versions limited to two characters. runlevels: lists runlevels for which action for this id should be taken. If no runlevels are listed, do action for all runlevels. action: describes which of several possible actions should be taken. process tells which process, if any, should be run when action on this line is performed.
  • 17. Runlevels , shutdown, and reboot inittab 17 Ex: Part 1 ## inittab This file describes how the INIT process should set up # the system in a certain run-level. ## Author: Miquel van Smoorenburg, <[email protected]> # Modified for RHS Linux by Marc Ewing and Donnie Barnes # # Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:5:initdefault: Before thinking runlevels, init runs the sysinit script. # System initialization. si::sysinit:/etc/rc.d/rc.sysinit
  • 18. Runlevels , shutdown, and reboot inittab 18 Ex: Part 2 l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 For actual runlevel chosen (before in id:5:initdefault), a script is run – in this case /etc/rc.d/rc 5. Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now Trapping Ctrl-Alt-Delete for keyboard system reboot. # Run gettys in standard runlevels 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 # Run xdm in runlevel 5 x:5:respawn:/etc/X11/prefdm -nodaemon In runlevel 2 ,3 , 4, 5, init verifies if the /etc/inittab as the following programs running: (mingetty handles terminal login, and mgetty handles modem dialin access)
  • 19. Runlevels , shutdown, and reboot inittab 19 Ex: Part 3 # When our UPS tells us power has failed, assume we have a few minutes # of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have powerd installed and your # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" Power failure settings.
  • 20. Runlevels , shutdown, and reboot Initialization scripts 20 Scripts used by init for: starting the system; shutting down; changing runlevels are typically in /etc/init.d or /etc/rc.d directory. There’s a series of symbolic links in rcn.d directories. One directory for each runlevel n, They control if the script is started and stopped when entering a runlevel. /etc/rc.d/rc 0 /etc/rc.d/rc 1 /etc/rc.d/rc 2 /etc/rc.d/rc 3 /etc/rc.d/rc 4 /etc/rc.d/rc 5 /etc/rc.d/rc 6 man init and man inittab
  • 21. Runlevels , shutdown, and reboot Init scripts 21 Ex: yourname@yourcomp~# find /etc -path "*rc[0-9]*.d/???au*" /etc/rc.d/rc2.d/S27auditd /etc/rc.d/rc2.d/K72autofs /etc/rc.d/rc4.d/S27auditd /etc/rc.d/rc4.d/S28autofs /etc/rc.d/rc5.d/S27auditd /etc/rc.d/rc5.d/S28autofs /etc/rc.d/rc0.d/K72autofs /etc/rc.d/rc0.d/K73auditd /etc/rc.d/rc6.d/K72autofs /etc/rc.d/rc6.d/K73auditd /etc/rc.d/rc1.d/K72autofs /etc/rc.d/rc1.d/K73auditd /etc/rc.d/rc3.d/S27auditd /etc/rc.d/rc3.d/S28autofs yourname@yourcomp~# cd /etc/rc.d/rc5.d yourname@yourcomp rc5.d# ls -l ???a* lrwxrwxrwx 1 root root 16 2008-04-07 11:29 S27auditd -> ../init.d/auditd lrwxrwxrwx 1 root root 16 2008-04-01 07:51 S28autofs -> ../init.d/autofs lrwxrwxrwx 1 root root 15 2008-04-01 14:03 S44acpid -> ../init.d/acpid lrwxrwxrwx 1 root root 13 2008-04-01 07:50 S95atd -> ../init.d/atd lrwxrwxrwx 1 root root 22 2008-04-01 07:54 S96avahi-daemon -> ../init.d/avahi-daemon lrwxrwxrwx 1 root root 17 2008-11-17 13:40 S99anacron -> ../init.d/anacron The links have: K (stopped) or S (Started); two-digit number (priority), name of service Here audit and autofs services have Knn entries in all runlevels and Snn entries for runlevels 3 and 5. S indicates that the service is started when that runlevel is entered, K indicates that it should be stopped. nn component of link name indicates priority order in which the service should be started or stopped. In example, audit is started before autofs, and it is stopped later.
  • 22. Runlevels , shutdown, and reboot Init vs. Upstart 22 Traditional method of booting a Linux system is based on UNIX System V init process. For systems where everything is known and connected when the system starts it works well 1st Involves loading initial RAM disk (initrd) 2nd passing control to a program called init (init program is installed as part of sysvinit package) 3rd init program runs a series of scripts in a predefined order to bring up the system. If something that is expected is not available, the init process typically waits for it. Modern systems with hot-pluggable devices, network file systems, present new challenges. waiting for hardware that may come available later, is not desirable. An alternative initialization process was first introduced in Ubuntu 6.10 ("Edgy Eft") in 2006. It’s called upstart Has supplanted the init process in Ubuntu, Fedora, and others, with vestiges of init remaining and still in use http://upstart.ubuntu.com/
  • 23. Runlevels , shutdown, and reboot Upstart 23 In contrast to the static init scripts the upstart system is driven by events. Events triggered by hardware changes, started or stoped tasks, by processes on the system. Example: connecting a USB drive might cause udev service to send a block-device-added event, which would cause a defined task to check /etc/fstab and mount the drive. upstart initialization program replaces /sbin/init. •Upstart jobs are defined in /etc/init directory and subdirectories. •upstart system will process /etc/inittab and System V init scripts. New Fedora /etc/inittab contains only id entry for initdefault; New Ubuntu does not have /etc/inittab (must create one to specify a default runlevel). Events used to trigger tasks or services (known as jobs).
  • 24. Runlevels , shutdown, and reboot Upstart 24 Upstart has command initctl Gives interaction with upstart init daemon. (start or stop jobs, list jobs, get status of jobs, emit events, restart init process) Ex: yourname@yourcomp~# initctl list rc stop/waiting tty (/dev/tty3) start/running, process 1486 tty (/dev/tty2) start/running, process 1484 tty (/dev/tty6) start/running, process 1492 tty (/dev/tty5) start/running, process 1490 tty (/dev/tty4) start/running, process 1488 plymouth-shutdown stop/waiting control-alt-delete stop/waiting system-setup-keyboard start/running, process 1000 readahead-collector stop/waiting vpnc-cleanup stop/waiting quit-plymouth stop/waiting rcS stop/waiting prefdm start/running, process 1479 init-system-dbus stop/waiting ck-log-system-restart stop/waiting readahead stop/waiting ck-log-system-start stop/waiting start-ttys stop/waiting readahead-disable-services stop/waiting ck-log-system-stop stop/waiting rcS-sulogin stop/waiting serial stop/waiting