This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: [artdodge@cs.bu.edu] libc/1220: The code in resolv/res_send.c is not thread-safe
- To: aj@arthur.rhein-neckar.de
- Subject: Re: [artdodge@cs.bu.edu] libc/1220: The code in resolv/res_send.c is not thread-safe
- From: Mark Kettenis <kettenis@wins.uva.nl>
- Date: Sun, 25 Jul 1999 01:37:43 +0200 (CEST)
- CC: libc-alpha@sourceware.cygnus.com, artdodge@cs.bu.edu
- References: <u87lnpvf6w.fsf@arthur.rhein-neckar.de>
From: Andreas Jaeger <aj@arthur.rhein-neckar.de>
Date: 25 Jul 1999 00:46:47 +0200
We've got the appended bug report about res_send.c not being
thread-safe.
The resolver is indeed not thread safe. This is a known issue, and
not easy to solve. The new BIND 8.2 allegedly comes with a
thread-safe resolver, that has a new (thread-safe) interface. But as
far as I know, nobody is working on integration with glibc. To
complicate matters there are some cryptography issues too. I don't
think we'll have a thread-safe resolver before glibc 2.2.
Mark