[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <em2f4c5b21-0d16-4148-a95d-f2b1a425dc0e@4d66d709.com>
Date: Sat, 20 Sep 2025 16:33:11 +0000
From: "Laurent Bercot" <ska-dietlibc@...rnet.org>
To: musl@...ts.openwall.com
Subject: Re[2]: closefrom and close_range wrappers
>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.
If the event is not the child's death, then the child needs to know
the fd in order to close it. If it is a known fd, then the wrapper can
close it as well. If the number of the fd is transmitted through a
complex protocol that the wrapper cannot intercept, that's pretty bad
architecture and a pretty bad place to insert a wrapper, and at this
point close_range is just providing the pig with a vanity mirror to help
it put the lipstick on.
--
Laurent
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.
