Issues on OSX - Jaguar

Maybe your current directory isn't in your path. Try a full path or use
./psql when sitting in the directory.

---------------------------------------------------------------------------

Robert J. Sanford, Jr. wrote:

I find this to be odd, very odd...

I'm running Marc Liyange's binary package for OSX.

I installed Jaguar yesterday and was halfway expecting to have issues with
PostgreSQL. Well, not quite like I thought I would. I looked at the process
viewer and discovered that the backend really is running. I conneced with
DbVisualizer and got all of the data out of there. Life is good. But...

I can' run psql from the command line. I get an error that says "psql:
command not found". At first I thought it might have my path screwed up so I
went directly into /usr/local/bin and tried to run psql from there. Same
message.

I shut down everything and reinstalled using the latest distro from Marc
Liyange that is marked as being for Jaguar and got the same thing.

I cannot invoke the postmaster from the command line either. Very odd
considering that the postmaster is running from startup.

I think I'm missing something here. Any ideas?

rjsjr

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Okay, I'm a *nix newb. A friend just pointed out that I should try ./psql
and that worked. I acted under the assumption that the current directory was
considered part of the path as it is in Windows (unfortunately my current
fiscal lifeblood). Sigh.

rjsjr

From one *NIX newb to another --

Okay, I'm a *nix newb. A friend just pointed out that I should try ./psql
and that worked. I acted under the assumption that the current directory was
considered part of the path as it is in Windows (unfortunately my current
fiscal lifeblood). Sigh.

Having the current directory in your path by default is considered to be
a security hazard in *NIX. (Ought to be okay in your own directories,
but who knows what lurks in some of the directories you might cd to.)

Near as I can tell, the newer versions of MSWindows seem to at least be
pushing the current directory down to the end of the default path list.

--
Joel Rees <joel@alpsgiken.gr.jp>

On Thu, 05 Sep 2002 16:43:11 -0400
pgsql-general-owner@postgresql.org wrote:

I can' run psql from the command line. I get an error that says "psql:
command not found". At first I thought it might have my path screwed up so I
went directly into /usr/local/bin and tried to run psql from there. Same
message.

I cannot invoke the postmaster from the command line either. Very odd
considering that the postmaster is running from startup.

This seems to have to do with your PATH setting.
Check with "echo $PATH" how your path is set.

Moreover check what psql actually is: on my system (Debian Linux) it is
a symbolic link to pg_wrapper.

Moreover the default shell on Mac OSX is tcsh, which is probably not
what you want (C-shell variants are inappropriate for scripting).
AFAIK tcsh uses a hash map for looking up commands; this map is
rebuilt with the command "rehash".

It is generally wise to change the default shell to zsh (a strongly
improved version of the Bourne shell). The system wide startup file
of zsh is /etc/profile, which is *not* read by tcsh.

Hope this helps

Christoph Dalitz

In article <DLEOKEMOOBGOBOHDJBAMMEDACPAA.rsanford@trefs.com>,
"Robert J. Sanford, Jr." wrote:

Okay, I'm a *nix newb. A friend just pointed out that I should try ./psql
and that worked. I acted under the assumption that the current directory was
considered part of the path as it is in Windows (unfortunately my current
fiscal lifeblood). Sigh.

Hello Robert,

this would be very unsecure, imagine a user on a multi-user host had
a small shell-script named "ls", which would invoke "rm -rf /".

When root entered this directory and tried to have a look at it's contents
with "ls" and the current directory (".") would be the first entry in the
path, root could erase the whole disc!

Best Regards
Mirko