Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!decvax!decwrl!pyramid!uccba!hal!ncoast!robertd
From: robertd@ncoast.UUCP (Rob DeMarco)
Newsgroups: comp.unix.questions
Subject: Re: $PATH glitch? -- Gould Powernode
Message-ID: <4092@ncoast.UUCP>
Date: Fri, 7-Aug-87 21:52:08 EDT
Article-I.D.: ncoast.4092
Posted: Fri Aug  7 21:52:08 1987
Date-Received: Sun, 9-Aug-87 11:17:31 EDT
References: <155@dsacng1.UUCP> <6175@brl-smoke.ARPA>
Reply-To: robertd@ncoast.UUCP (Rob DeMarco)
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 25
Keywords: PATH shell environment

In article <6175@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <155@dsacng1.UUCP> naa1810@dsacng1.UUCP (Bill Bereza) writes:
>>I further experimented and found out that I could not execute a
>>new shell script that I created in my bin directory from any directory
>>path except when my cwd was my bin directory.
>
>Sounds like you corrupted your $PATH.  The reason it worked
>when your cwd was your bin directory is that then the "." or
>"" in your $PATH found the command.

    This same thing happened to me. When I create a new shell script and put it
in my bin directory. It wount execute except when I am IN the directory. This
would remain in effect untill I logged off or called up csh again. I just
excepted that and tried to live with it. I guest cshell (and shell too?)
stores those files in memory so it doesn't have to keep physically searching
for a command and waist time. Can some one offer help in why it really does
this?

		[> Rd
-- 
North Coast Computer Resources(ncoast) - 216-781-6201 (or 781-6202)

UUCP:decvax!cwruecmp!ncoast!robertd

Sysop: NEODG (login "sbbs")