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

ps aux | grep script_Name

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

kill -9 1787 787

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

如果您在远程服务器上，请使用top检查内存使用情况，并找到您的进程及其ID。之后，只需执行kill[您的进程ID]。

假设您正在使用nohup执行java程序，您可以通过

`ps aux | grep java`

输出

xxxxx     9643  0.0  0.0  14232   968 pts/2   

然后您可以通过输入来终止该进程

sudo kill 9643

或者让我们说，您需要杀死所有的Java进程，然后使用

sudo killall java

该命令将终止所有Java进程。您可以将此用于流程。只需在命令末尾给出进程名

sudo killall {processName}

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

如果您的应用程序总是使用相同的端口，您可以像这样终止该端口中的所有进程。

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

今天我遇到了同样的问题。因为是很久以前的事了，我完全忘了我在什么时候用了哪个命令。我尝试了三种方法:

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.

一旦找到进程的PID，就可以使用kill PID来终止进程。