Skip to Content.
Sympa Menu

freetds - Re: [freetds] Strange TODO

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] Strange TODO
  • Date: Fri, 25 Jul 2008 17:31:12 +0200

>
> >
> > Thus spake Frediano:
> >
> > > How to fix all these problems??
> > > - we have no safe source for servent_data (private libc
> > header is not
> > > installed). - we can implement a thread-safe
> getservbyname locking
> > > _servent_mutex directly and call getservbyname_r (not that
> > clean) and
> > > endservent_r (avoid leaks). - use getaddrinfo, is it
> > thread-safe under
> > > NetBSD ??
> >
> > It turns out we're going about this all wrong. Instead of
> > getservbyname_r
> > et al., we should be using getnameinfo/getaddrinfo. Those should be
> > threadsafe on any platform, and are standard.
> >
> > Do you think it's feasible to abandon getservbyname_r? Do we
> > support any
> > platform on which getservbyname_r is implemented but
> > getaddrinfo is not?
> >
> > --jkl
> >
>
> Yes, we can do. The problem is that some getaddrinfo
> implementations (FreeBSD or NetBSD if
> I remember) are NOT threadsafe !! But well... perhaps
> nowadays these platforms are quite
> old...
>

Referring to
http://www.freebsd.org/cgi/man.cgi?query=getaddrinfo&apropos=0&sektion=3&manpath=NetBSD+4.
0&format=html
from NetBSD 4.0 and FreeBSD 6.0 these functions are thread-safe (not fully
before :( )

freddy77

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.24.

Top of Page