你可以试试

kill -9 `pgrep [command name]`

关于失去你的油灰:通常是ps…| awk / grep / perl /…流程也会被匹配!老把戏是这样的

ps -ef | grep -i [n]ohup 

这样正则表达式搜索就不会与正则表达式搜索过程匹配!

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

这适用于mi fine在mac上

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

你可以试试

kill -9 `pgrep [command name]`

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

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