Skip to Content.
Sympa Menu

freetds - RE: pool server build

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: pool server build
  • Date: Mon, 14 Oct 2002 09:16:31 -0400


Sure, we all agree with you that this should be fixed, it's just a question
of time and priorities. If this is important to you, submit a patch that
fixes it. We'll make sure it gets applied.

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Monday, October 14, 2002 5:44 AM
To: TDS Development Group
Subject: [freetds] RE: pool server build



>> 1. The program is full of "fprintf(stderr, ... )" and there is no way
>> to turn of this _extremely_ verbose stderr logging, like a #define or
>> something similar.
>
> ./tdspool [poolname] 2> /dev/null
>
> Seriously, this is on the todo list.

Yes, in bash.

Still, I would feel much better if this was #ifdef:ed or made
a command line swich. As it was mentioned earlier on the list,
95% of the time TDS spent, even _without_ using debugging was in
the tds_debug-code.


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.






Archive powered by MHonArc 2.6.24.

Top of Page