Re: [PATCH v2] transport-helper, connect: add atexit handler to reap children on abnormal exit

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 11, 2026, 19:38 UTC
Message-ID: <xmqqfr66nol8.fsf@gitster.g>
In-Reply-To: <CAGVkMb6M2buc5zS+SFfYa6LLs7fN369MrVagETVg0U_PN7njOg@mail.gmail.com>

Andrew Au <cshung@gmail.com> writes:

Show 8 quoted lines

> Thank you for the feedback.
>
> The use case is a long-running service running as PID 1 inside a
> container. The service continuously spawns git to detect repository
> changes — it is not a one-shot container where git itself is the
> primary process. Because the service is meant to stay alive
> indefinitely, any zombies git leaves behind accumulate over time
> rather than being cleaned up when the container exits.

Wait, the proposed log message said "Git is the pid 1", and now the above is "there is some long-running service that runs Git". Which one is it? Wouldn't that long-running service be the right process that should reap these unwaited children? Or is "git" used as that long-running service somehow?