Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Troubleshooting CentOS

You're reading from   Troubleshooting CentOS A practical guide to troubleshooting the CentOS 7 community-based enterprise server

Arrow left icon
Product type Paperback
Published in Jun 2015
Publisher
ISBN-13 9781785289828
Length 190 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Jonathan Hobson Jonathan Hobson
Author Profile Icon Jonathan Hobson
Jonathan Hobson
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Troubleshooting CentOS
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Basics of Troubleshooting CentOS FREE CHAPTER 2. Troubleshooting Active Processes 3. Troubleshooting the Network Environment 4. Troubleshooting Package Management and System Upgrades 5. Troubleshooting Users, Directories, and Files 6. Troubleshooting Shared Resources 7. Troubleshooting Security Issues 8. Troubleshooting Database Services 9. Troubleshooting Web Services 10. Troubleshooting DNS Services Index

Issuing the kill signal


The most common reason behind wanting to know a process ID is to pass this information to the kill command. The process ID does have other uses, but our primary concern is to remove a problematic service or application by issuing a termination signal (SIGTERM) to the relevant daemon as follows:

# kill pid_of_process

The kill signal instructs the process to terminate, thereby enabling the process in question to perform some basic cleanup operations and exit in an orderly fashion. This approach is known as a "safe kill". However, depending on your situation, a better solution can be to force a service or application to hang up, and thereby enable an automatic reload of the daemon as follows:

# kill -1 pid_of_process

This command is known as a SIGHUP or hangover command. On the other hand, if the process has seemingly crashed, and a safe kill or reload operation fails to make any difference, then by passing the following command, you will be able to literally kill the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images