Bruce Momjian wrote:
> Marc G. Fournier wrote:
> >
> > After hearing that FreeBSD wasn't thread safe, I posted to the FreeBSD
> > lists to find out what is up ...
> >
> > FreeBSD 5.x has a getpwuid_r function that should be used ... and, the
> > word I got from one of the developers was that geta
Marc G. Fournier wrote:
>
> After hearing that FreeBSD wasn't thread safe, I posted to the FreeBSD
> lists to find out what is up ...
>
> FreeBSD 5.x has a getpwuid_r function that should be used ... and, the
> word I got from one of the developers was that getaddrinfo(3) should be
> used instead
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Hm. A quick grep shows that our *only* use of gethostbyname is in
>> src/port/getaddrinfo.c. Seems like we should omit this "porting
>> requirement" on platforms that have getaddrinfo.
> See the post I just made --- fe-secure.c calls
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > FreeBSD 5.x has a getpwuid_r function that should be used ... and, the
> > word I got from one of the developers was that getaddrinfo(3) should be
> > used instead of gethostbyname ...
>
> Hm. A quick grep shows that our *only*
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> FreeBSD 5.x has a getpwuid_r function that should be used ... and, the
> word I got from one of the developers was that getaddrinfo(3) should be
> used instead of gethostbyname ...
Hm. A quick grep shows that our *only* use of gethostbyname is in
s
After hearing that FreeBSD wasn't thread safe, I posted to the FreeBSD
lists to find out what is up ...
FreeBSD 5.x has a getpwuid_r function that should be used ... and, the
word I got from one of the developers was that getaddrinfo(3) should be
used instead of gethostbyname ...
Now, getpwuid_r
