FreeTDS Development Group

[James Cameron <james.cameron AT hp.com>]

On Fri, 2002-08-09 at 13:03, Brian Bruns wrote:
> Instead of dumping to stderr which might not be desirable in some 
> applications (PHP for instance) is it possible to use tds_client_msg() to 
> alert the upper layer app of the problem?

It's a confusing situation.

src/tds/login.c already uses perror() to report to stderr, the code
there also uses a client message, and people already know to look at the
Apache error log.

Before my proposed patch, a failure to resolve a name should have
resulted in a "Server %s not found!" client message only.  But a
connection failure results in the stderr output.  Should this be a
client message?

Also, I'm not sure yet where the bogus IP is coming from.  My review of
the lookup_host() path suggested that it would always return an empty
string as an IP if it could not resolve a name.

Or is it just data left in ip_addr member of config struct that isn't
ever cleared after alloc()?  I think I'll find out once Casey replies.

-- 
James Cameron                                     (james.cameron AT hp.com)

http://quozl.linux.org.au/         (or)         http://quozl.netrek.org/