I did a quick perusal of the source (and compared it against the NetBSD
tree) and it looks like the easiest way to
make getaddrinfo() thread safe is to TURN OFF Yellow Pages (pee).
NetBSD changes the only variable globals to local (in they yp code by
removing the caching optimization) and puts
On Fri, Dec 11, 2009 at 12:20:30PM -0700, Brad Davis wrote:
I did a quick perusal of the source (and compared it against the
NetBSD tree) and it looks like the easiest way to
make getaddrinfo() thread safe is to TURN OFF Yellow Pages (pee).
NetBSD changes the only variable globals to local
I did a quick perusal of the source (and compared it against the NetBSD
tree) and it looks like the easiest way to
make getaddrinfo() thread safe is to TURN OFF Yellow Pages (pee).
NetBSD changes the only variable globals to local (in they yp code by
removing the caching optimization) and
2009/12/11 Theo de Raadt dera...@cvs.openbsd.org:
I did a quick perusal of the source (and compared it against the NetBSD
tree) and it looks like the easiest way to
make getaddrinfo() thread safe is to TURN OFF Yellow Pages (pee).
NetBSD changes the only variable globals to local (in they yp
Am 08.12.2009 um 15:52 schrieb Bret Lambert:
The existing resolver code is compleat balls, as oga@ would spell it.
Frankly, it needs to be dragged behind the chemical sheds and
quietly suffocated.
Wouldn't it be possible to at least put a lock around it, so that at
least it does not
Am 08.12.2009 um 15:41 schrieb Otto Moerbeek:
Nobody did the work yet. If it's very important to you, consider
spending effort making it thread safe. I believe netbsd and freebsd
have thread safe implementations. But actullay verifying that is
pretty hard.
Yes, the NetBSD implementation is
On Wed, Dec 9, 2009 at 10:55 AM, Jonathan Schleifer
js-openbsd-m...@webkeks.org wrote:
Am 08.12.2009 um 15:52 schrieb Bret Lambert:
The existing resolver code is compleat balls, as oga@ would spell it.
Frankly, it needs to be dragged behind the chemical sheds and
quietly suffocated.
On Wed, Dec 9, 2009 at 10:56 AM, Jonathan Schleifer
js-openbsd-m...@webkeks.org wrote:
Am 08.12.2009 um 15:41 schrieb Otto Moerbeek:
Nobody did the work yet. If it's very important to you, consider
spending effort making it thread safe. I believe netbsd and freebsd
have thread safe
On Wed, Dec 09, 2009 at 10:56:58AM +0100, Jonathan Schleifer wrote:
Am 08.12.2009 um 15:41 schrieb Otto Moerbeek:
Nobody did the work yet. If it's very important to you, consider
spending effort making it thread safe. I believe netbsd and freebsd
have thread safe implementations. But
Just wondering: Why is getaddrinfo breaking POSIX by not being thread-
safe and what is the thread-safe alternative to it? (Please don't tell
me to use locks, as that would kill the possibility to lookup multiple
hosts at once).
I consider it very strange that an OS still has a thread
On Tue, Dec 08, 2009 at 02:44:27PM +0100, Jonathan Schleifer wrote:
Just wondering: Why is getaddrinfo breaking POSIX by not being
thread-safe and what is the thread-safe alternative to it? (Please
don't tell me to use locks, as that would kill the possibility to
lookup multiple hosts at once
On Tue, Dec 8, 2009 at 3:41 PM, Otto Moerbeek o...@drijf.net wrote:
On Tue, Dec 08, 2009 at 02:44:27PM +0100, Jonathan Schleifer wrote:
Just wondering: Why is getaddrinfo breaking POSIX by not being
thread-safe and what is the thread-safe alternative to it? (Please
don't tell me to use locks
12 matches
Mail list logo
