freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "James K. Lowden" <jklowden AT schemamania.org>
- To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: AW: [freetds] connect problem to mssql 7.0
- Date: Fri, 19 Dec 2003 01:06:24 -0500
On Thu, 18 Dec 2003, "Roland Bole" <Samlinux AT gmx.at> wrote:
> >
> > Try these, to clarify which tsql you're finding:
> >
> > $ command -V tsql; tsql -C
> > tsql is /usr/local/bin/tsql
> > locale is "C"
> > using default charset "ISO-8859-1"
> > Compile-time settings (established with the "configure" script):
...
>
> $ command -V tsql; tsql -C
>
> i don't have such a command: "command -V" ???
> is this a special tool ?
No. It's the Posix-defined built-in that every shell is supposed to
support. "command -[vV]" is the standard command to print what path a
given executable is found on.
Many people are familiar with which(1), but that's an external binary.
Only the shell itself knows its mechanism for interpreting a command, so
only a shell built-in can tell you what the shell will launch when you
type "tsql" (or anything else).
$ bash --version; which tsql
GNU bash, version 2.05.0(1)-release (i386--netbsdelf)
Copyright 2000 Free Software Foundation, Inc.
/usr/local/bin/tsql
$ help command
command: command [-pVv] command [arg ...]
Runs COMMAND with ARGS ignoring shell functions. If you have a shell
function called `ls', and you wish to call the command `ls', you can
say "command ls". If the -p option is given, a default value is used
for PATH that is guaranteed to find all of the standard utilities. If
the -V or -v option is given, a string is printed describing COMMAND.
The -V option produces a more verbose description.
--jkl
-
[freetds] Problem displaying Results
, (continued)
-
[freetds] Problem displaying Results,
Quique Luna, 12/18/2003
-
Re: [freetds] Problem displaying Results,
Frediano Ziglio, 12/18/2003
- RE: [freetds] Problem displaying Results, Quique Luna, 12/18/2003
-
Re: [freetds] Problem displaying Results,
Frediano Ziglio, 12/18/2003
-
RE: AW: [freetds] connect problem to mssql 7.0,
Frediano Ziglio, 12/18/2003
-
RE: AW: [freetds] connect problem to mssql 7.0,
Roland Bole, 12/18/2003
- RE: AW: [freetds] connect problem to mssql 7.0, Frediano Ziglio, 12/18/2003
-
RE: AW: [freetds] connect problem to mssql 7.0,
Roland Bole, 12/18/2003
-
RE: AW: [freetds] connect problem to mssql 7.0,
Lowden, James K, 12/18/2003
- RE: AW: [freetds] connect problem to mssql 7.0, Frediano Ziglio, 12/18/2003
-
RE: AW: [freetds] connect problem to mssql 7.0,
Lowden, James K, 12/18/2003
-
RE: AW: [freetds] connect problem to mssql 7.0,
Roland Bole, 12/18/2003
-
Re: AW: [freetds] connect problem to mssql 7.0,
James K. Lowden, 12/19/2003
-
AW: AW: [freetds] connect problem to mssql 7.0,
Roland Bole, 12/19/2003
-
Re: AW: AW: [freetds] connect problem to mssql 7.0,
Frediano Ziglio, 12/19/2003
- AW: AW: AW: [freetds] connect problem to mssql 7.0, Roland Bole, 12/19/2003
- AW: AW: AW: [freetds] connect problem to mssql 7.0, Roland Bole, 12/19/2003
-
Re: AW: AW: [freetds] connect problem to mssql 7.0,
Frediano Ziglio, 12/19/2003
-
AW: AW: [freetds] connect problem to mssql 7.0,
Roland Bole, 12/19/2003
-
Re: AW: [freetds] connect problem to mssql 7.0,
James K. Lowden, 12/19/2003
-
RE: AW: [freetds] connect problem to mssql 7.0,
Roland Bole, 12/18/2003
-
[freetds] Problem displaying Results,
Quique Luna, 12/18/2003
Archive powered by MHonArc 2.6.24.