使用 bash 和正则表达式在一行中查找并终止进程

发布于 2024-09-15 05:30:22 字数 444 浏览 5 评论 0原文

我在编程时经常需要杀死一个进程。

我现在的做法是：

[~]$ ps aux | grep 'python csp_build.py'
user    5124  1.0  0.3 214588 13852 pts/4    Sl+  11:19   0:00 python csp_build.py
user    5373  0.0  0.0   8096   960 pts/6    S+   11:20   0:00 grep python csp_build.py
[~]$ kill 5124

如何自动提取进程ID并在同一行中杀死它？

像这样：

[~]$ ps aux | grep 'python csp_build.py' | kill <regex that returns the pid>

原文

I often need to kill a process during programming.

The way I do it now is:

[~]$ ps aux | grep 'python csp_build.py'
user    5124  1.0  0.3 214588 13852 pts/4    Sl+  11:19   0:00 python csp_build.py
user    5373  0.0  0.0   8096   960 pts/6    S+   11:20   0:00 grep python csp_build.py
[~]$ kill 5124

How can I extract the process id automatically and kill it in the same line?

Like this:

[~]$ ps aux | grep 'python csp_build.py' | kill <regex that returns the pid>

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

哭了丶谁疼 2024-09-22 05:30:22

在 bash 中，仅使用问题⁽¹⁾中列出的基本工具，您应该能够执行以下操作：

kill $(ps aux | grep '[p]ython csp_build.py' | awk '{print $2}')

其工作原理的详细信息如下：

ps 为您提供所有进程的列表。
grep 根据您的搜索字符串进行过滤，[p] 是一种阻止您获取实际 grep 进程本身的技巧。
awk 只是为您提供每行的第二个字段，即 PID。
$(x) 构造意味着执行 x 然后获取其输出并将其放在命令行上。上面构造中的 ps 管道的输出是进程 ID 列表，因此您最终会得到类似 kill 1234 1122 7654 的命令。

这是显示其实际操作的文字记录：

pax> sleep 3600 &
[1] 2225
pax> sleep 3600 &
[2] 2226
pax> sleep 3600 &
[3] 2227
pax> sleep 3600 &
[4] 2228
pax> sleep 3600 &
[5] 2229
pax> kill $(ps aux | grep '[s]leep' | awk '{print $2}')
[5]+  Terminated              sleep 3600
[1]   Terminated              sleep 3600
[2]   Terminated              sleep 3600
[3]-  Terminated              sleep 3600
[4]+  Terminated              sleep 3600

您可以看到它终止了所有睡眠者。

更详细地解释 grep '[p]ython csp_build.py' 位：当您执行 sleep 3600 & 后跟 ps -ef | grep sleep，您往往会得到两个个带有 sleep 的进程，sleep 3600 和 grep sleep< /code> （因为它们都有睡眠，这不是火箭科学）。

但是，ps -ef | grep '[s]leep' 不会创建一个包含 sleep 的 grep 进程，而是使用命令 grep '[ 创建一个进程s]leep' 这就是棘手的一点：grep 找不到那个，因为它正在寻找正则表达式“字符类 [s] 中的任何字符” （基本上就是 s），然后是 leep

换句话说，它正在寻找 sleep 但 grep 过程是 sleep。 code>grep '[s]leep' 其中没有文本 sleep

当我看到这个（由 SO 上的某人）时，我立即开始使用它，因为。

这比添加 | grep -v grep 少了一个过程，而且
又很狡猾，是一种罕见的组合:-)

⁽¹⁾; 不仅限于使用这些基本工具，有一个漂亮的 pgrep 命令，它可以根据特定条件查找进程（当然，假设您的系统上有它）。

例如，您可以使用 pgrep sleep 输出所有 sleep 命令的进程 ID（默认情况下，它与进程名称匹配）。如果您想匹配整个命令行，如 ps 所示，您可以执行 pgrep -f 'sleep 9999' 之类的操作。

顺便说一句，如果您执行 pgrep pgrep，它不会列出自身，因此在这种情况下不需要上面显示的棘手过滤方法。

您可以使用 -a 显示完整的进程名称来检查这些进程是否是您感兴趣的进程。您还可以使用 -u 或 -U 将范围限制为您自己的进程（或一组特定的用户）。有关更多选项，请参阅 pgrep/pkill 的 man 页面。

一旦您满意，它只会显示您感兴趣的进程，然后您可以使用具有相同参数的 pkill 向所有这些进程发送信号。

In bash, using only the basic tools listed in your question⁽¹⁾, you should be able to do:

kill $(ps aux | grep '[p]ython csp_build.py' | awk '{print $2}')

Details on its workings are as follows:

The ps gives you the list of all the processes.
The grep filters that based on your search string, [p] is a trick to stop you picking up the actual grep process itself.
The awk just gives you the second field of each line, which is the PID.
The $(x) construct means to execute x then take its output and put it on the command line. The output of that ps pipeline inside that construct above is the list of process IDs so you end up with a command like kill 1234 1122 7654.

Here's a transcript showing it in action:

pax> sleep 3600 &
[1] 2225
pax> sleep 3600 &
[2] 2226
pax> sleep 3600 &
[3] 2227
pax> sleep 3600 &
[4] 2228
pax> sleep 3600 &
[5] 2229
pax> kill $(ps aux | grep '[s]leep' | awk '{print $2}')
[5]+  Terminated              sleep 3600
[1]   Terminated              sleep 3600
[2]   Terminated              sleep 3600
[3]-  Terminated              sleep 3600
[4]+  Terminated              sleep 3600

and you can see it terminating all the sleepers.

Explaining the grep '[p]ython csp_build.py' bit in a bit more detail: when you do sleep 3600 & followed by ps -ef | grep sleep, you tend to get two processes with sleep in it, the sleep 3600 and the grep sleep (because they both have sleep in them, that's not rocket science).

However, ps -ef | grep '[s]leep' won't create a grep process with sleep in it, it instead creates one with the command grep '[s]leep' and here's the tricky bit: the grep doesn't find that one, because it's looking for the regular expression "any character from the character class [s] (which is basically just s) followed by leep.

In other words, it's looking for sleep but the grep process is grep '[s]leep' which doesn't have the text sleep in it.

When I was shown this (by someone here on SO), I immediately started using it because

it's one less process than adding | grep -v grep; and
it's elegant and sneaky, a rare combination :-)

⁽¹⁾ If you're not limited to using those basic tools, there's a nifty pgrep command which will find processes based on certain criteria (assuming you have it available on your system, of course).

For example, you can use pgrep sleep to output the process IDs for all sleep commands (by default, it matches the process name). If you want to match the entire command line as shown in ps, you can do something like pgrep -f 'sleep 9999'.

As an aside, it doesn't list itself if you do pgrep pgrep, so the tricky filter method shown above is not necessary in this case.

You can check that the processes are the ones you're interested in by using -a to show the full process names. You can also limit the scope to your own processes (or a specific set of users) with -u or -U. See the man page for pgrep/pkill for more options.

Once you're satisfied it will only show the processes you're interested in, you can then use pkill with the same parameters to send a signal to all those processes.

使用 bash 和正则表达式在一行中查找并终止进程

如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

评论（30）

一行：

额外：

One liner:

Bonus:

使用 ps 命令的 -C 标志

第一种情况，简单的命令

第二种情况，搜索 cmd

Using -C flag of ps command

1st case, simple command

2nd case, search for cmd

关于作者

相关话题

热门标签

推荐作者

謌踐踏愛綪

开始看清了

高速公鹿

alipaysp_PLnULTzf66

热情消退

白色月光

友情链接

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

使用 `ps` 命令的 `-C` 标志

Using `-C` flag of `ps` command