Skip to main content

Documentation Index

Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt

Use this file to discover all available pages before exploring further.

In this lesson, you’ll learn how to manage system services with Upstart, switch runlevels, and handle system shutdowns and reboots. We’ll cover core commands, scheduling techniques, and best practices for both Upstart and systemd environments.

​
Controlling Services with Upstart

Upstart job definitions reside in /etc/init. You can list all available services and their current states (including PIDs) using initctl list: 
$ sudo initctl list
avahi-cups-reload            stop/waiting
avahi-daemon                 start/running, process 1123
mountall-net                 stop/waiting
mountnfs-bootclean.sh        start/running
nmbd                         start/running, process 3085
passwd                       stop/waiting
Upstart jobs live under /etc/init. To add or modify a job, create or edit its .conf file in this directory.
Use these commands to control services:
CommandActionExample
start <job>Start the servicesudo start tty6
stop <job>Stop the servicesudo stop tty6
status <job>Show state and PIDsudo status tty6
$ sudo start tty6
$ sudo status tty6
tty6 start/running, process 3282
$ sudo stop tty6

​
Querying and Switching Runlevels

Although Upstart doesn’t use /etc/inittab, you can still use the legacy commands: 
$ runlevel        # Display current and previous runlevel
$ sudo telinit 3  # Switch to runlevel 3
Note: Runlevels 0 and 6 correspond to halt and reboot in System V–style init.

​
System Shutdown and Reboot

The shutdown utility wraps System V runlevel transitions with extra safeguards:
  • Broadcasts a warning to all logged-in users
  • Blocks new logins during shutdown
  • Sends SIGTERM then SIGKILL to processes
  • Transitions to runlevel 0 (halt) or 6 (reboot)
By default, shutdown without -h or -r switches to single-user mode (runlevel 1).

​
Scheduling a Shutdown

The <time> argument is mandatory and accepts:
FormatDescriptionExample
hh:mmSpecific 24-hour time02:00
+mMinutes from now+20
now/+0Immediate shutdownnow
Optionally include a broadcast message: 
$ sudo shutdown 02:00
$ sudo shutdown +20 "System maintenance in 20 minutes"
$ sudo shutdown now "Shutdown initiated"
Scheduling or initiating a shutdown requires root privileges. Ensure you have the proper permissions before running these commands.

​
SysV vs. systemd Commands

On System V–based distributions, shutdown handles power actions. On systemd-based systems, use the following equivalents:
ActionSysV Commandsystemd Command
Rebootsudo shutdown -r nowsudo systemctl reboot
Power offsudo shutdown -h nowsudo systemctl poweroff
For Ctrl+Alt+Delete behavior on SysV, you can limit authorized users in /etc/shutdown.allow.

​
Broadcasting Messages with wall

If you only need to notify users without shutting down: 
$ sudo wall "System going into maintenance mode in 5 minutes!"

Watch Video