Date: Mon, 09 Aug 1999 23:31:13 -0600 From: Wes Peters <wes@softweyr.com> To: ognir@humboldt1.com Cc: louie@TransSys.COM, steve_tarkalson@hotmail.com, bmcgover@cisco.com, dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: gethostbyaddr() and threads. Message-ID: <37AFB921.D3070875@softweyr.com> References: <199908092354.QAA18586@home.humboldt1.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Joe Groff wrote:
>
> ---Louis A. Mamakos said:
> >> You could malloc() a struct hostent for each call to
> >> gethostby*(), each time registering the hostent in some list along with the
> >> thread's PID. If the same thread calls gethostby*, use the same buffer, or
> >> allocate a new one if another thread calls it. Have a static function be
> > called
> >> atexit to free all the mallocs.
> >
> > Yuk!
> >
> > If you're writing a multithreaded program, a slightly different API for
> > gethostbyname() is likely to be the least of your worries.
> >
> Yeah, that IS a horrible idea of mine. :) Changing the API should be a last
> resort, though, since we don't want to introduce to many FreeBSDisms into the
> already-fragmented-enough Unix world.
>
> Just a thought, how does Linux's GNU libc handle gethostby* in threaded apps?
Probably the way POSIX specifies, which would certainly be *our* target.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
http://softweyr.com/ wes@softweyr.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37AFB921.D3070875>