How to get the process ID to kill a nohup process?

Question 1

When using nohup and you put the task in the background, the background operator (&) will give you the PID at the command prompt. If your plan is to manually manage the process, you can save that PID and use it later to kill the process if needed, via kill PID or kill -9 PID (if you need to force kill). Alternatively, you can find the PID later on by ps -ef | grep "command name" and locate the PID from there. Note that nohup keyword/command itself does not appear in the ps output for the command in question.

If you use a script, you could do something like this in the script:

nohup my_command > my.log 2>&1 &
echo $! > save_pid.txt

This will run my_command saving all output into my.log (in a script, $! represents the PID of the last process executed). The 2 is the file descriptor for standard error (stderr) and 2>&1 tells the shell to route standard error output to the standard output (file descriptor 1). It requires &1 so that the shell knows it's a file descriptor in that context instead of just a file named 1. The 2>&1 is needed to capture any error messages that normally are written to standard error into our my.log file (which is coming from standard output). See I/O Redirection for more details on handling I/O redirection with the shell.

If the command sends output on a regular basis, you can check the output occasionally with tail my.log, or if you want to follow it "live" you can use tail -f my.log. Finally, if you need to kill the process, you can do it via:

kill -9 `cat save_pid.txt`
rm save_pid.txt

Question 2

I am using red hat linux on a VPS server (and via SSH - putty), for me the following worked:

First, you list all the running processes:

ps -ef

Then in the first column you find your user name; I found it the following three times:

One was the SSH connection
The second was an FTP connection
The last one was the nohup process

Then in the second column you can find the PID of the nohup process and you only type:

kill PID

(replacing the PID with the nohup process's PID of course)

And that is it!

I hope this answer will be useful for someone I'm also very new to bash and SSH, but found 95% of the knowledge I need here :)

Question 3

suppose i am running ruby script in the background with below command

nohup ruby script.rb &

then i can get the pid of above background process by specifying command name. In my case command is ruby.

ps -ef | grep ruby

output

ubuntu   25938 25742  0 05:16 pts/0    00:00:00 ruby test.rb

Now you can easily kill the process by using kill command

kill 25938

Question 4

jobs -l should give you the pid for the list of nohup processes. kill (-9) them gently. ;)

Question 5

You could try

kill -9 `pgrep [command name]`

Question 6

Suppose you are executing a java program with nohup you can get java process id by

`ps aux | grep java`

output

xxxxx     9643  0.0  0.0  14232   968 pts/2

then you can kill the process by typing

sudo kill 9643

or lets say that you need to kill all the java processes then just use

sudo killall java

this command kills all the java processes. you can use this with process. just give the process name at the end of the command

sudo killall {processName}

Question 7

If your application always uses the same port, you can kill all the processes in that port like this.

kill -9 $(lsof -t -i:8080)

Question 8

This works in Ubuntu

Type this to find out the PID

ps aux | grep java

All the running process regarding to java will be shown

In my case is

johnjoe      3315  9.1  4.0 1465240 335728 ?      Sl   09:42   3:19 java -jar batch.jar

Now kill it kill -9 3315

The zombie process finally stopped.

Question 9

when you create a job in nohup it will tell you the process ID !

nohup sh test.sh &

the output will show you the process ID like

you can kill it then :

kill 25013

Question 10

I started django server with the following command.

nohup manage.py runserver <localhost:port>

This works on CentOS:

:~ ns$netstat -ntlp
:~ ns$kill -9 PID

Question 11

I often do this way. Try this way :

ps aux | grep script_Name

Here, script_Name could be any script/file run by nohup. This command gets you a process ID. Then use this command below to kill the script running on nohup.

kill -9 1787 787

Here, 1787 and 787 are Process ID as mentioned in the question as an example. This should do what was intended in the question.

Question 12

If you are unaware of the PID, then first find it using TOP command

top -U userid

PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

You will get the PID using top, then perform the kill operation.

$ kill -9 <PID>

Question 13

Today I met the same problem. And since it was a long time ago, I totally forgot which command I used and when. I tried three methods:

Using the STIME shown in ps -ef command. This shows the time you start your process, and it's very likely that you nohup you command just before you close ssh(depends on you) . Unfortunately I don't think the latest command is the command I run using nohup, so this doesn't work for me.
Second is the PPID, also shown in ps -ef command. It means Parent Process ID, the ID of process that creates the process. The ppid is 1 in ubuntu for process that using nohup to run. Then you can use ps --ppid "1" to get the list, and check TIME(the total CPU time your process use) or CMD to find the process's PID.
Use lsof -i:port if the process occupy some ports, and you will get the command. Then just like the answer above, use ps -ef | grep command and you will get the PID.

Once you find the PID of the process, then can use kill pid to terminal the process.

Question 14

This works for mi fine on mac

kill -9 `ps -ef | awk '/nohup/{ print \$2 }'`

Question 15

About losing your putty: often the ps ... | awk/grep/perl/... process gets matched, too! So the old school trick is like this

ps -ef | grep -i [n]ohup

That way the regex search doesn't match the regex search process!

Question 16

if you are on a remote server, check memory usage with top , and find your process and its ID. After that, just execute kill [your process ID] .