Date: Wed, 29 Sep 2021 13:48:51 -0700
From: "Pawel S. Veselov" <pawel.vese...@gmail.com>
Message-ID: <72a4f226-78dc-22f9-4d4b-90e434b76...@gmail.com>
| I think the only way to fix this is to have the resolver state
| cleaned up thoroughly after fork(). I can't see how this can be
| worked around by applications.
Maybe put a call to res_init() in the child, immediately after a successful
fork (before any other fd manipulation).
That will try to close the old kqueue, which will fail, but no-one cares,
and then open a new one.
kre
