Skip to Content.
Sympa Menu

freetds - RE: [freetds] mssql_connect fails with PHP 4.3.4 on RH Linux 9

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] mssql_connect fails with PHP 4.3.4 on RH Linux 9
  • Date: Tue, 2 Dec 2003 14:35:23 -0500

> From: James McGowan [mailto:jmcgowan AT luxurylink.com]
> Sent: December 2, 2003 2:00 PM
> >
> > I issued:
> >
> > export TDSDUMP=/var/log/tdsdump
> >
> > and the environment variable is present, however nothing is
> > being logged. (I even did a reboot to load a new kernel.)
> > Another quick question on logging... I've had:
> >
> > dump file append = /var/log/freetds
> >
> > in freetds.conf for a while now, and again, no logging.

One of two things.

A) "dump file append" is a yes/no variable; the name of the log file is
determined by "dump file" or TDSDUMP. That variable defaults to "no" and
would stay that way until a proper "yes" appears. It may be your log file
is being overwritten. Is there no file, or a zero-length file?

(Hmm. You're the second fellow today (and maybe the third all year) bitten
by an erroneous freetds.conf entry.)

B) If there's no log file, and
1. "dump file = /var/log/freetds", and
2. "/var/log/freetds" is a filename, and
3. the process has permission to write to "/var/log",

then I'd check your PHP (or apache?) executable with ldd(1) to make sure
FreeTDS is being linked in. The log file is opened as soon as FreeTDS
begins searching for its configuration files.

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page