[freetds] Dreaded "Server SYBASE not found!" question

Frediano Ziglio freddy77 at gmail.com
Wed Dec 16 08:03:02 EST 2009

2009/12/12 James K. Lowden <jklowden at freetds.org>:
> Nelson, Erik - 2 wrote:
>> There's an outstanding todo in login.c to open the log file prior to
>> tds_set_server() where "SYBASE" is being set in to
>> connection->server_name, but it's not at all clear why the server
>> name/IP aren't being set correctly since the server info is clearly
>> being found in freetds.conf.
> ...
>> [Hiruko] found in "/modleng/usr/etc/odbc.ini"
>> found this section:
>>         [Hiruko]
>>         Driver  =       FreeTDS
>>         Description     =       DataDirect 5.1 SQL Server Wire Protocol
>>         Servername      =       Hiruko
>>         Server  =       Hiruko
>>         Port    =       1433
> Server and Servername cannot be in the same section.  One overrides the
> other.
> This highlights a more general question, for which I'd like to hear
> suggestions (and/or see a patch!) from anyone who's interested.
> We have two mutually exclusive attributes in our configuration files.  In
> odbc.ini we have server/servername; in freetds.conf we have port/instance.
>  These inevitably trip up some people, probably a lot more than write to
> the list, who over-specify the sever.  What to do?
> One solution is to die noisily with err(3) when invalid combinations are
> found for the requested server.  (Also, perhaps warnings writting to
> stderr for any other configuration problems e.g. invalid property names).

Yesterday I applied a patch in ODBC that give error suing wrong
combinations of DSN/SERVER/SERVERNAME. Error is quite explicit. My
isql does not print the error (grrrr...).


More information about the FreeTDS mailing list