blocks|key|1652561|text|您必须使子进程守护进程，以便在父进程被杀死(或死亡)时将其杀死，否则它们将被init(1)采用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1652562|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You have to make the sub processes daemonic in order to have them killed when the father is killed (or dies), otherwise they are adopted by init(1).

blocks|key|1579618|text|不，父进程被终止时，子进程不一定会被终止。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1579619|但是，如果子进程打开了一个它正在写入的管道，并且父进程正在读取数据，那么当它下一次尝试写入该管道时，它将获得一个SIGPIPE，对于该管道，默认操作是终止它。这是实践中经常发生的事情。|1579620|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

No, child processes are not necessarily killed when the parent is killed.

However, if the child has a pipe open which it is writing to and the parent is reading from, it will get a SIGPIPE when it next tries to write to the pipe, for which the default action is to kill it. That is often what happens in practice.

blocks|key|1579696|text|在UNIX上，父进程和子进程的生命周期之间没有强制关系。严格地说，进程只有在调用exit()或接收到默认操作要终止的未处理信号时才会终止。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1579697|然而，当用户在该终端上点击ctrl-C、ctrl-\等时，“控制终端”中的整个“前台进程组”可以接收像SIGINT和SIGQUIT这样的信号。特定的行为部分由登录shell实现(在tty驱动程序的帮助下)。细节可能相当复杂:查看here和here|offset|length|1579698|entityMap|0|LINK|mutability|MUTABLE|url|http://www.linusakesson.net/programming/tty/index.php|1|http://www.win.tue.nl/~aeb/linux/lk/lk-10.html^0|0|36|4|0|3B|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]|$D|U|E|V|1|W]]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|O]]]]

On UNIX, there is no enforced relation between parent and child process's lifetimes. Strictly speaking, process will only terminate when they call exit() or receive an unhandled signal for which default action is to terminate. 

However, an entire "foreground process group" in a "controlling terminal" can receive signals like SIGINT and SIGQUIT when the user hits ctrl-C, ctrl-\, etc. on that terminal. Specific behaviour is partly implemented by the login shell (with help from the tty driver). Details may be quite complicated: look <a href="http://www.linusakesson.net/programming/tty/index.php" rel="nofollow noreferrer">here</a> and <a href="http://www.win.tue.nl/~aeb/linux/lk/lk-10.html" rel="nofollow noreferrer">here</a>

blocks|key|1654421|text|如果你关闭了进程的父进程id终端pid，那么终端就被关闭了。当终端关闭时，它的所有进程也会被杀死。但是如果你在shell中创建了一个子shell，那么如果你创建了任何进程并杀死了该进程的ppid，那么只有那个子shell会被杀死，并且它们的孩子会变成孤儿。它们的父类变为init，pid为1。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1654422|见习生@SIPL+~$+ps+-ef+%7C+grep睡眠见习生3893+3870+0+10:55分/1+00:00:00+:00睡眠4000见习生3895+3788+0+10:55分/0+00:00:00+grep+--color=自动睡眠见习生@SIPL+~$+kill+-9+3870见习生@SIPL+~$+ps+-ef+%7C+grep睡眠见习生3893+1+0+10:55分/1+00:00:00+:00:00睡眠见习生3906+3788+0+10:55分/0+00:00:00+grep+--color=自动睡眠|1654423|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If u close the terminal pid which is the parent process id of the process then terminal is closed. And when terminal is closed then all its processes also gets killed. But if u create a sub shell in shell then if u create any process and kill ppid of that process then only that sub shell kill and their child becomes orphans. Their parent becomes init and pid is 1.

[trainee@SIPL ~]$ ps -ef | grep sleep trainee 3893 3870 0 10:55 pts/1 00:00:00 sleep 4000 trainee 3895 3788 0 10:55 pts/0 00:00:00 grep --color=auto sleep [trainee@SIPL ~]$ kill -9 3870 [trainee@SIPL ~]$ ps -ef | grep sleep trainee 3893 1 0 10:55 pts/1 00:00:00 sleep 4000 trainee 3906 3788 0 10:55 pts/0 00:00:00 grep --color=auto sleep

blocks|key|352869|text|您只需要知道您想要终止哪个进程或服务。在我的例子中，httpd是。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|352870|killall+-9+httpd|code-block|syntax|javascript|352871|它将杀死httpd的所有子进程。|352872|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You just need to know which process or service you wanna kill. In my case httpd is.

<pre><code>killall -9 httpd
</code></pre>

It will kill all the child processes of httpd.

One of my colleague told me this morning, when he killed <a href="http://supervisord.org/" rel="noreferrer">supervisord</a> by "kill -9", the subprocesses of supervisord is not killed.

He is quite sure about that, but I tried many times and did not find that happen.

So when a parent process is killed by "kill -9", will linux ensure that it's sub-processes also been killed?

When a parent process is killed by "kill -9", will subprocess also be killed?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我的一个同事今天早上告诉我，当他用"kill -9“杀死时，supervisord的子进程并没有被杀死。他很确定这一点，但我尝试了很多次，都没有发现这一点。那么，当父进程被"kill -9“杀死时，linux会确保它的子进程也被杀死吗？

问当父进程被"kill -9“杀死时，子进程也会被杀死吗？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当父进程被"kill -9“杀死时，子进程也会被杀死吗？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当父进程被"kill -9“杀死时，子进程也会被杀死吗？
EN