Re: systemd-resolved support

2023-11-25 Thread Cristian Rodríguez via curl-library
On Sat, Nov 25, 2023 at 9:56 AM Max Kellermann wrote: > On Sat, Nov 25, 2023 at 1:32 PM Cristian Rodríguez > wrote: > > resolved is designed to be spoken to as a normal dns caching resolver or > using dbus. > > I don't believe adding a dbus communication backend will improve your > situation.

Re: systemd-resolved support

2023-11-25 Thread Max Kellermann via curl-library
On Sat, Nov 25, 2023 at 1:32 PM Cristian Rodríguez wrote: > resolved is designed to be spoken to as a normal dns caching resolver or > using dbus. > I don't believe adding a dbus communication backend will improve your > situation. I think you are not aware that libcurl already sends all its

Re: systemd-resolved support

2023-11-25 Thread Cristian Rodríguez via curl-library
On Fri, Nov 24, 2023 at 4:36 PM Max Kellermann via curl-library < curl-library@lists.haxx.se> wrote: > Hi, > we recently had a problem with libcurl: due to a DNS server problem, > an attempt to cancel a libcurl request blocked the whole I/O event > loop of a server process because libcurl was

Re: systemd-resolved support

2023-11-24 Thread Dan Fandrich via curl-library
On Fri, Nov 24, 2023 at 08:25:05PM +0100, Max Kellermann via curl-library wrote: > For the long term, I was wondering whether libcurl would be interested > in incorporating a systemd-resolved mode if I were to submit a pull > request. Wouldn't it work to simply switch to c-ares for resolving

systemd-resolved support

2023-11-24 Thread Max Kellermann via curl-library
Hi, we recently had a problem with libcurl: due to a DNS server problem, an attempt to cancel a libcurl request blocked the whole I/O event loop of a server process because libcurl was waiting for the resolver thread to finish (inside pthread_join()), causing a major outage of a service. We use