Em 09/06/2025 08:20, Natanael Copa escreveu:
Generally speaking, you need a proper pid 1 process doing this. crond (or any
other daemon) should not need to worry about this problem.
This is VERY true.
On Unix, orphans are not(*) re-parented by walking back the process
tree: they are re-parented to the process root (pid 1) directly. And
containers need a decent pid 1 very very often, not just for proper
orphan process handling, but also for sane signal broadcasting.
But really, crond is expected to be a long-running process, and it is a
process dispatcher. Not protecting its process table from undue growth
by an unexpected zombie pile-up is Not A Good Idea.
Sure, complain in the system log (*with a rate limiter*) if your process
dispatcher does keep track of its children and it is not supposed to be
pid 1. Been there, done that. But Reap Them All[tm] nonetheless.
So I am very much in favor of the proposed fix.
(*) Unless you have something like the Linux
prctl(PR_SET_CHILD_SUBREAPER) in use.
--
Henrique de Moraes Holschuh
Analista de Projetos
Centro de Estudos e Pesquisas em Tecnologias de Redes e Operações
(Ceptro.br)
+55 11 5509-3537 R.:4023
INOC 22548*625
www.nic.br
_______________________________________________
busybox mailing list
[email protected]
https://lists.busybox.net/mailman/listinfo/busybox
