跳至主要内容

How to Kill

I always use some new release of Linux distribution, so some software froze from time to time. In order to restart it, kill command can be very handy to use for it so fast and saves lot of time compared with UI prompt.
So today, we learn how to kill effectively.

Kill

First, we should understand how to use kill. But we are surprised to find the man kill only tell us the common format:

$ kill [signal or option] PID(s)

But what’s the signal? Which one should I choose?
Signal is a kind of inter-process communication which we can take it as a message sent between processes.
And we usually use the following three signals:

Signal Name     Signal Value            Behaviour
SIGHUP                1             Hangup
SIGKILL               9             Kill Signal
SIGTERM               15            Terminate

Some kinds of signal can be ignored, like SIGTERM; but some can’t, like SIGKILL. So what we commonly use is the following:

kill -9 pid

Find the PID

Now, we know the basic about kill. So how to get the pid?
We can try the following three commands:

$ps aux | grep 'NAME'
...
$pidof NAME
...
$pgrep NAME
...

Kill By Name

Besides to kill by pid, we can also kill be name.

$pkill -9 NAME

And if we don’t know the name of a process, but we know the process id by viewing the result of ps (which seems not so common and convenient though).

ps -p 1337 -o command=

Here, the process is selected by its PID with -p. The -o option specifies the output format, comm meaning the command name.

It seems more convenient to use process name to kill. But sometimes, we don’t know the name exactly, if we choose the wrong process, we may screw our work. And in some other cases, the named process has many other siblings or child process, we may prefer kill just one of them (e.g. the names process is Java, and we just want to kill one of instances of jvm)

Last Word

Now we are ready to kill. But before we step ahead and really execute a kill command, we should understand that a process is like a file, it belongs to some user and have permission control:

  • A user can kill all his process.
  • A user can not kill another user’s process.
  • A user can not kill processes System is using.
  • A root user can kill System-level-process and the process of any user.

Ref

Written with StackEdit.

评论

此博客中的热门博文

Spring Boot: Customize Environment

Spring Boot: Customize Environment Environment variable is a very commonly used feature in daily programming: used in init script used in startup configuration used by logging etc In Spring Boot, all environment variables are a part of properties in Spring context and managed by Environment abstraction. Because Spring Boot can handle the parse of configuration files, when we want to implement a project which uses yml file as a separate config file, we choose the Spring Boot. The following is the problems we met when we implementing the parse of yml file and it is recorded for future reader. Bind to Class Property values can be injected directly into your beans using the @Value annotation, accessed via Spring’s Environment abstraction or bound to structured objects via @ConfigurationProperties. As the document says, there exists three ways to access properties in *.properties or *.yml : @Value : access single value Environment : can access multi...

LevelDB Source Reading (1): Structure

LevelDB Source Reading (1): Structure LevelDB “is an open source on-disk key-value store.” After I read some documents, I have some basic understanding of LevelDB. So I come up with some questions about structure of LevelDB to answer when reading the source code. Structure Log File: repair/recover db A log file (*.log) stores a sequence of recent updates. Each update is appended to the current log file. The log file contents are a sequence of 32KB blocks. The only exception is that the tail of the file may contain a partial block. Block format: Each block consists of a sequence of records: block := record* trailer? record := checksum: uint32 // crc32c of type and data[] ; little-endian length: uint16 // little-endian type: uint8 // One of FULL, FIRST, MIDDLE, LAST data: uint8[length] // data is LengthPrefixedSlice with type from batch data definition in Block : data: also named `writeBatch` in levelDB // WriteBatch header has an 8-byte ...

LevelDB Source Reading (3): Compaction

LevelDB Source Reading (3): Compaction In the last blog that analyzes read/write process of Leveldb, we can see writing only happens to log file and memory table, then it relies on the compaction process to move the new updates into persistent sorted table for future use. So the compaction is a crucial part for the design, and we will dive into it in this blog. Compaction LevelDB compacts its underlying storage data in the background to improve read performance. The upper sentence is cited from the document of Leveldb , and we will see how it is implemented via code review. Background compaction // db_impl.cc void DBImpl :: MaybeScheduleCompaction ( ) { // use background thread to run compaction env_ - > Schedule ( & DBImpl :: BGWork , this ) ; } Two main aspects // arrange background compaction when Get, Open, Write void DBImpl :: BackgroundCompaction ( ) { // compact memtable CompactMemTable ( ) ; // compact ...