FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

It may not be quite that simple.  The configure flag "--enable-threadsafe"
defines the macros _REENTRANT and _THREAD_SAFE. These are used in system
header files to determine whether reentrancy is needed.  So if you don't use
"--enable-threadsafe" you may not get reentrant system code.

We have a way to specify that the normal gethostby*() calls are already
reentrant.  Arrange for SOCK_REENTRANT to be defined in
tds_sysdep_private.h.in on your platform.  (This macro should probably be
renamed to NETDB_REENTRANT to accurately reflect the behavior it
defines...I'll likely do that today).

Unfortunately that's not quite good enough...configure will fail if you
specify "--enable-threadsafe" and it doesn't find gethostby*_r() functions.
I will look at how to handle this...either by moving the SOCK_REENTRANT
[NETDB_REENTRANT] detection into configure, or simply by removing the
configure-time failure in this case (we already have build-time checks in
threadsafe.c that will ensure consistency.)

However, with the checks for libd4r that I added a couple of days ago, this
really isn't a pressing issue right now...it will find and use the
gethostby*_r() functions in that library, as long as "--enable-threadsafe"
is used.  It's not really important that the man pages suggest that this
interface should no longer be used -- as long as it still works.

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
Sent: Wednesday, October 16, 2002 1:22 AM
To: TDS Development Group
Subject: [freetds] Re: TDSFREE on HPUX--- " There is not enough memor y
available now"

But I think the solution is: don't try.  FreeTDS is, with one exception that
I can think of, written to be threadsafe.  The purpose of
"--enable-threadsafe" is to control its calls to the OS.  In your case the
"old" calls are themselves threadsafe.  So, no need to use
"--enable-threadsafe".  


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.