[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aM6yv4xRaMGY508g@voyager>
Date: Sat, 20 Sep 2025 15:57:19 +0200
From: Markus Wichmann <nullplan@....net>
To: musl@...ts.openwall.com
Subject: Re: closefrom and close_range wrappers
Am Sat, Sep 20, 2025 at 11:45:41AM +0000 schrieb Laurent Bercot:
> If the parent is a wrapper program, shouldn't it have the exact same
> behaviour as its child, and in particular exit (as close an
> approximation as possible of) when the child does, with (a close
> approximation of) the same exit code?
>
> Wrappers wrap everything, and events that usually trigger on a program's
> death will this time trigger on the wrapper's death. This is expected
> behaviour, and I don't think it's a valid use case for close_range.
>
> --
> Laurent
>
I think he was talking about a case where the wrapper's parent and child
are trying to communicate some sort of event through FD closure, and the
event is not necessarily the child's death. A use case might be a DHCP
client signalling to a network manager that a lease was obtained,
without using Freedesktop COM, I mean D-Bus. The DHCP client must
continue to run to renew the lease when it ends. Although the common
solution in the DHCP clients I am aware of is to background the program,
which would also make the wrapper exit.
Ciao,
Markus
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
