pool server build

Magnus Ahl Magnus.Ahl at infogate.se
Mon Oct 14 12:44:11 EDT 2002



>> 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.

>> 2. The program behaves very strange on one of our servers (RedHat 8.0) in
>> the way that it keeps all connections alive until the program is
forcefully
>> killed. Reverting from gcc 3.2 to gcc 2.95.3 and rebuilding the program
and
>> the library does not fix this problem.

> That is strange behaviour, if you posted details, we might be able to do
> something with it.

	I'm sorry, but that is about all detail I have. One experiment on
	a limited platform. Perhaps this will surface sometime later when
	more and more peopla start to migraet to and develop on the RH 8.0
	platform?


regards,

 Infogate AB             Magnus.Ahl at infogate.se
 Storgatan 29                   tel: 035-171970
 Box 345                      mobil: 702-118265
 301 08 Halmstad                www.infogate.se




More information about the FreeTDS mailing list