make test fails

Brian Bruns camber at umcc.ais.org
Mon Mar 20 22:47:37 EST 2000



It's defined in sys/select.h which is included from sys/types.h which is in
the file.  Try a two step compile to see if its a header or linker problem

gcc -o passthru.o -c passthru.c
gcc -o passthru passthru.o

Brian

On Mon, 20 Mar 2000, John Dejournett wrote:

> Brian,
> 
> Minor problem with passthru.c.  When I compile gcc can not find the
> functions FD_ZERO, FD_SET, or FD_ISSET.  Is there a .h file or otherwise
> that I need to be linking against for these functions?
> 
> Sincerely,
> John DeJournett
> HP ScanJet Developer Support
> HP_SCAN at greeley.sykes.com
> Fax: (970) 346-2254
> 
> 
> 
> 		-----Original Message-----
> 		From:	Brian Bruns [mailto:camber at umcc.ais.org]
> 		Sent:	Friday, March 17, 2000 7:02 PM
> 		To:	TDS Development Group
> 		Subject:	[freetds] RE:  make test fails
> 
> 		 << File:  >> 
> 		Ok, now things get a bit complicated :-)
> 
> 		I'm attaching a file called 'passthru.c'.  Edit it with the
> IP address and
> 		port of you server (lines 38 & 40) and compile with
> something like 
> 		'gcc -o passthru passthru.c'.  Then on your Win box add an
> entry for the
> 		bogus SQL Server on your linux box (port 4000 by default,
> you can change it
> 		to 1433 if it makes life easier).
> 
> 		Now run the passthru server:
> 
> 		$ ./passthru > passthru.log
> 
> 		Then attempt to connect from the Win box.
> 
> 		Send me the log and we'll see what we get!
> 
> 		Brian
> 
> 		On Fri, 17 Mar 2000, John Dejournett wrote:
> 
> 		> Brian, 
> 		> 
> 		> Sorry, I was typing without thinking.  According to the
> local SA, the server
> 		> uses server logins.
> 		> 
> 		> Sincerely,
> 		> John DeJournett
> 		> HP ScanJet Developer Support
> 		> HP_SCAN at greeley.sykes.com
> 		> Fax: (970) 346-2254
> 		> 
> 		> 
> 		> 
> 		> 		-----Original Message-----
> 		> 		From:	Brian Bruns
> [mailto:camber at umcc.ais.org]
> 		> 		Sent:	Friday, March 17, 2000 4:55 PM
> 		> 		To:	TDS Development Group
> 		> 		Subject:	[freetds] RE:  make test
> fails
> 		> 
> 		> 
> 		> 
> 		> 		On Fri, 17 Mar 2000, John Dejournett wrote:
> 		> 
> 		> 		> Brian,
> 		> 		> 
> 		> 		> Sorry it took a while to respond, but I
> wanted to make
> 		> sure that I had
> 		> 		> accurate information.  I have confirmed
> that the server is
> 		> using domain
> 		> 		> logins.  
> 		> 		> 
> 		> 		Ok, there's the problem then. SQL Server
> must be configured
> 		> with 'server
> 		> 		logins'.  Domain logins don't work, as the
> linux box is not
> 		> a member of the
> 		> 		domain among other technical reasons that I
> don't even
> 		> altogether fathom
> 		> 		(domains work on DCE/RPC over SMB, so some
> sort of
> 		> integration with the
> 		> 		samba client would most likely be required
> to make it work).
> 		> 
> 		> 		So, two options, turn on server logins or
> use an ODBC-ODBC
> 		> bridge product
> 		> 		(which requires software on both linux and
> NT sides).
> 		> 
> 		> 		Of course, I'd happily accept patches for
> making domain
> 		> logins work :-) (or
> 		> 		even network traces of a domain login would
> be great!) 
> 		> 
> 		> 		Brian
> 		> 		> Generally the server is accessed from
> windows platforms
> 		> via ODBC.  The setup
> 		> 		> process we use is as follows
> 		> 		> 
> 		> 		> 1.	install the MS-SQL client
> configuration utility.
> 		> 		> 2.	Install 32-bit ODBC (latest
> revision)
> 		> 		> 3.	Configure ODBC as follows:
> 		> 		> *	Data source name: SIMS
> 		> 		> *	Description:		Blank
> 		> 		> *	Server:		Server's IP address
> 		> 		> *	Network Address	Server's IP address,
> Port
> 		> 		> *	Network Library	DBMSSOCN
> 		> 		> 4.	Configure the SQL Client
> Configuration utility as
> 		> follows:
> 		> 		> *	Server:		Server's IP address
> 		> 		> *	DLL Name:		DBMSSOCN
> 		> 		> *	Connect String:	Server's IP address,
> Port
> 		> 		> 5.	Install one of the various DB front
> end packages we
> 		> use in-house.
> 		> 		> 6.	Configure front end to access DB
> server by the ODBC
> 		> Data Source
> 		> 		> Name.
> 		> 		> 
> 		> 		> The machines that connect to the DB server
> may be on one
> 		> of several domains,
> 		> 		> and the logins used in accessing the DB
> server are of a
> 		> different form from
> 		> 		> the domain logins.
> 		> 		> 
> 		> 		> Sincerely,
> 		> 		> John DeJournett
> 		> 		> 
> 		> 		> 
> 		> 		> 
> 		> 		> 		-----Original Message-----
> 		> 		> 		From:	Brian Bruns
> 		> [mailto:camber at umcc.ais.org]
> 		> 		> 		Sent:	Wednesday, March 15,
> 2000 7:58 PM
> 		> 		> 		To:	TDS Development
> Group
> 		> 		> 		Subject:	[freetds]
> RE:  make test
> 		> fails
> 		> 		> 
> 		> 		> 		John,
> 		> 		> 
> 		> 		> 		Hmmm...are you absolutely
> sure the server is
> 		> not using
> 		> 		> domain logins?  You
> 		> 		> 		said you were able to login
> from a different
> 		> client, can you
> 		> 		> provide some
> 		> 		> 		details on that (I'm
> assuming it is a Win
> 		> box, is it part of
> 		> 		> the NT
> 		> 		> 		domain...etc...)
> 		> 		> 
> 		> 		> 		I can't imagine we are that
> far away from
> 		> getting this...at
> 		> 		> worst I can
> 		> 		> 		provide you with a trace
> server to capture
> 		> the traffic and
> 		> 		> compare against
> 		> 		> 		what you see in the
> freetds.log
> 		> 		> 
> 		> 		> 		Brian
> 		> 		> 
> 		> 		> 		On Wed, 15 Mar 2000, John
> Dejournett wrote:
> 		> 		> 
> 		> 		> 		> Brian,
> 		> 		> 		> 
> 		> 		> 		> The platform is Slackware
> Linux (Intel).
> 		> I know that the
> 		> 		> server is running
> 		> 		> 		> at least NT4.0 SP5, but I
> don't think I
> 		> would bet on it
> 		> 		> being any more
> 		> 		> 		> current than that.  The
> MSSQL is version
> 		> 6.5.
> 		> 		> 		> 
> 		> 		> 		> I just build SQSH, and it
> did build
> 		> correctly against the
> 		> 		> libraries (with a
> 		> 		> 		> little help from the FAQ
> page), but I
> 		> don't know that I am
> 		> 		> using it
> 		> 		> 		> correctly.  The command
> line that I am
> 		> using is: sqsh -D
> 		> 		> DBName -S
> 		> 		> 		> ServerName (from the
> interfaces file) -U
> 		> UserName
> 		> 		> 		> 
> 		> 		> 		> SQSH responds with the
> standard banner and
> 		> a password
> 		> 		> prompt.  I enter my
> 		> 		> 		> password, and the program
> shuts down
> 		> without reporting any
> 		> 		> error or
> 		> 		> 		> otherwise status
> information.  Am I going
> 		> about this
> 		> 		> incorrectly for
> 		> 		> 		> interactive mode?  SQSH
> may be seeing the
> 		> same problem as
> 		> 		> the test programs,
> 		> 		> 		> but without further
> confirmation I would
> 		> hesitate to make
> 		> 		> that assumption.
> 		> 		> 		> 
> 		> 		> 		> I don't particularly want
> to give up on
> 		> FreeTDS for this
> 		> 		> project (time not
> 		> 		> 		> being an issue), but that
> this point I am
> 		> starting to
> 		> 		> wonder if I shouldn't
> 		> 		> 		> backtrack and look at
> using an ODBC for
> 		> the database
> 		> 		> connectivity.  Am I
> 		> 		> 		> just beating a dead horse
> here, or do you
> 		> think that this
> 		> 		> is something that
> 		> 		> 		> is potentially resolvable
> if we keep
> 		> working at it?
> 		> 		> 		> 
> 		> 		> 		> Sincerely,
> 		> 		> 		> John DeJournett
> 		> 		> 		> 
> 		> 		> 		> 
> 		> 		> 		> 
> 		> 		> 		>
> -----Original Message-----
> 		> 		> 		> 		From:
> Brian Bruns
> 		> 		> [mailto:camber at umcc.ais.org]
> 		> 		> 		> 		Sent:
> Tuesday, March 14,
> 		> 2000 6:45 PM
> 		> 		> 		> 		To:	TDS
> Development
> 		> Group
> 		> 		> 		> 		Subject:
> [freetds]
> 		> Re: make test
> 		> 		> fails
> 		> 		> 		> 
> 		> 		> 		> 		Ok, looks
> exactly like a bad
> 		> 		> username/password pair...Out of
> 		> 		> 		> curiousity
> 		> 		> 		> 		which
> platform is this on
> 		> (Linux Intel?).
> 		> 		> Also what service
> 		> 		> 		> pack are you
> 		> 		> 		> 		running on
> the server side?
> 		> And...have
> 		> 		> attempted to compile
> 		> 		> 		> SQSH to see
> 		> 		> 		> 		if that
> works?
> 		> 		> 		> 
> 		> 		> 		> 		This is
> certainly a good
> 		> one.
> 		> 		> 		> 
> 		> 		> 		> 		Brian
> 		> 		> 		> 
> 		> 		> 		> 		On Mon, 13
> Mar 2000, John
> 		> Dejournett wrote:
> 		> 		> 		> 
> 		> 		> 		> 		> Brian,
> 		> 		> 		> 		> 
> 		> 		> 		> 		> I am
> attaching my FreeTDS
> 		> log file.  I
> 		> 		> have edited it a
> 		> 		> 		> little for obvious
> 		> 		> 		> 		> security
> reasons.  I may
> 		> have the user
> 		> 		> name and password
> 		> 		> 		> transposed since
> 		> 		> 		> 		> they are
> the same for this
> 		> particular
> 		> 		> account, but this
> 		> 		> 		> should reasonably
> 		> 		> 		> 		> accurate.
> 		> 		> 		> 		> 
> 		> 		> 		> 		> Sincerely,
> 		> 		> 		> 		> John
> DeJournett
> 		> 		> 		> 		> 
> 		> 		> 		> 		>
> <<tdslog.txt>> 
> 		> 		> 		> 		> 
> 		> 		> 		> 
> 		> 		> 
> 		> 		> 
> 		> 		> 		---
> 		> 		> 		You are currently subscribed
> to freetds as:
> 		> 		> johnde at greeley.sykes.com
> 		> 		> 		To unsubscribe, forward this
> message to
> 		> 		> $subst('Email.Unsub')
> 		> 		> 
> 		> 		> ---
> 		> 		> You are currently subscribed to freetds
> as: camber at ais.org
> 		> 		> To unsubscribe, forward this message to
> 		> $subst('Email.Unsub')
> 		> 		> 
> 		> 		> 
> 		> 
> 		> 
> 		> 		---
> 		> 		You are currently subscribed to freetds as:
> 		> johnde at greeley.sykes.com
> 		> 		To unsubscribe, forward this message to
> 		> $subst('Email.Unsub')
> 		> 
> 		> ---
> 		> You are currently subscribed to freetds as: camber at ais.org
> 		> To unsubscribe, forward this message to
> $subst('Email.Unsub')
> 		> 
> 		> 
> 
> ---
> You are currently subscribed to freetds as: camber at ais.org
> To unsubscribe, forward this message to $subst('Email.Unsub')
> 
> 




More information about the FreeTDS mailing list