FreeTDS Development Group

["Jay Sauls" <jaysauls AT hotmail.com>]

The plot thickens....

So just to be sure about which version of FreeTDS I was running, I did:

su
make uninstall

in my freetds directory, then I grabbed the following:

ftp://ftp.ibiblio.org/pub/Linux/ALPHA/freetds/freetds-current.tgz

and did the standard tar xzvf into a newly created /home/jays/freetds
directory, then did

./configure --with-ssl
make
su
make install

Then, I went to my sqsh directory, and did:

make
su
make install

Then, I setup a TDSDUMPCONFIG file.  That's when the interesting stuff
started to happen (note I changed the [jays] entry in freetds to
[jayssql] to avoid confusion with the username):

sqsh -S jayssql -U corp\\jays
sqsh-2.1 Copyright (C) 1995-2001 Scott C. Gray
This is free software with ABSOLUTELY NO WARRANTY
For more information type '\warranty'
Password:
Segmentation Fault


Here's what the tdsdumpconfig file looks like:
2002-10-07 16:07:17 Attempting to read conf files.
2002-10-07 16:07:17 Failed in reading conf file.  Trying interface
files.
2002-10-07 16:07:17 Looking for server....
2002-10-07 16:07:17 Looking for server in /home/jays/.interfaces
2002-10-07 16:07:17 Searching interfaces file /home/jays/.interfaces.
2002-10-07 16:07:17 Couldn't open /home/jays/.interfaces.
2002-10-07 16:07:17 Looking for server in /usr/local/interaces.
2002-10-07 16:07:17 Searching interfaces file /usr/local/interfaces.
2002-10-07 16:07:17 Couldn't open /usr/local/interfaces.
2002-10-07 16:07:17 Setting 'tmp_port' to 1433 as a guess.


So why is the conf file read failing?  I'd like to get ddd set up to
step through this, but I don't know how to configure the whole thing to
step through a library that's called by something else....   Note that
the segmentation fault doesn't occur if there is no TDSDUMPCONFIG
variable set....


-----Original Message-----
From: bounce-freetds-149810 AT franklin.oit.unc.edu
[mailto:bounce-freetds-149810 AT franklin.oit.unc.edu] On Behalf Of James
K. Lowden
Sent: Monday, October 07, 2002 3:43 PM
To: TDS Development Group
Subject: [freetds] Re: How to compile SQSH with FreeTDS .60?

On Mon, 7 Oct 2002 14:58:32 -0700, "Jay Sauls" <jaysauls AT hotmail.com>
wrote:
> Oops!  Sorry, I misspoke:
> 
> Using sqsh -S jays -U jays -I /home/jays/freetds.conf still gives:
> "Server jays not found!"
> 
> So it looks like sqsh isn't using the freetds.conf under any
> circumstances?

Jay, 

I sure hope you're enjoying this.  :)

The application, be it sqsh or tsql, doesn't typically control which
freetds.conf is used or how it's parsed (except tsql can bypass it, of
course).  If tsql can connect to servername "jays", then libtds is on
the
job.  

As Steve said, sqsh's '-I' parameter is for an old-fashioned
"interfaces"
file format.  Rather than try to coerce sqsh into using the right file,
I'd rather have sqsh rely entirely on FreeTDS to find and use the
freetds.conf.  

If you're not sure sqsh is using the right file, set TDSDUMPCONFIG. 
FreeTDS will write a log file describing the source of the configuration
it used.  

You can also test a standard login to Sybase's public server:

        [tsql|sqsh] -S JDBC -U guest -P sybase

as another way to isolate things.  

Steve mentioned 0.60.1.  Is that what you're using?  Just to double
check.
 

I'm a little puzzled.  As long as you're using the right version and
sqsh
is linked to it, you should have the same results Steve got.  It's too
bad
the prelogin logging doesn't show the login attempt.  That would make it
crystal clear.  

If you're sure everything is spot on, then the next thing to do, I
guess,
is to send us tcpdump(1) output of the login attempt.  That's not my
first
choice and it won't be fun to look at, but it's bound to turn up
something.  

Regards, 

--jkl

---
You are currently subscribed to freetds as: [jaysauls AT hotmail.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')