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.

如果你使用一个脚本，你可以在脚本中做这样的事情:

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.

如果该命令定期发送输出，您可以偶尔使用tail my.log检查输出，或者如果您希望“实时”跟踪它，则可以使用tail -f my.log。最后，如果你需要终止进程，你可以通过:

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

Jobs -l应该为您提供nohup进程列表的pid。 轻轻地杀死他们。 ；）

我经常这样做。试试这个方法:

ps aux | grep script_Name

这里，script_Name可以是nohup运行的任何脚本/文件。 这个命令为您提供一个进程ID。然后使用下面的命令终止在nohup上运行的脚本。

kill -9 1787 787

这里，1787和787是问题中举例提到的进程ID。 这应该达到问题的目的。

这在Ubuntu中是有效的

输入这个来找出PID

ps aux | grep java

所有有关java的运行过程将被显示

对我来说

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

现在杀死它杀死-9 3315

僵尸进程终于停止。

这适用于mi fine在mac上

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

你可以试试

kill -9 `pgrep [command name]`