From owner-freebsd-questions Mon Oct 4 11:40:11 1999 Delivered-To: freebsd-questions@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 10CA9154F1 for ; Mon, 4 Oct 1999 11:40:05 -0700 (PDT) (envelope-from godfreja@primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id LAA08753; Mon, 4 Oct 1999 11:39:56 -0700 (MST) Received: from usr03.primenet.com(206.165.6.203) via SMTP by smtp04.primenet.com, id smtpdAAAwpaiVq; Mon Oct 4 11:39:35 1999 Date: Mon, 4 Oct 1999 13:39:36 -0500 (CDT) From: Jason Godfrey To: chris@tourneyland.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 3.3-Release - problem with PATH? In-Reply-To: <3.0.6.32.19991004132156.008e3850@mail.9netave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you using csh (or one of it's offspring)? They scan your PATH and keep a list of available porgrams when you log in. If you add a program it won't show up untill a new scan is done. (In your case by loggin back in.) To force a rescan issue the command rehash And it should work. Other shells may be the same way, but I do not know. On Mon, 4 Oct 1999 chris@tourneyland.com wrote: > I guess I should have been more clear - the problem isn't that I can't run > programs in the current directory, it's that I can't run programs on the path. > > It seems like the problem is that if I install a program on the path, I > can't run it until I logout and log back in. It's as if all the programs on > the path are stored in some sort of database that the shell is consulting, > and new installs don't get committed to this db until I log out. That would > be kind of silly, so I'll bet it's something else, but at any rate that's > what it's acting like. > > Thanks though, > Chris > > At 04:37 PM 10/4/99 +0200, you wrote: > >On [19991003 23:46], Kent Stewart (kstewart@3-cities.com) wrote: > >>chris@tourneyland.com wrote: > >>> > >>> I just upgraded from 3.2 Release to 3.3 Release. No problems, except it > >>> seems that now my PATH variable is being ignored. My PATH is just fine, > >>> except trying to execute anything on the path (e.g. bash) gives me > 'command > >>> not found'. Using the full path name works fine. > >>> > >>It is the kind of response you get when "." isn't in your path. I > >>personally don't have dot in my path and I have to run via ./program. > > > >>From a security perspective that's the best thing to do. > > > >Using a . in your PATH makes you way less careful about running unknown > >programs. > > > >So I always recommend not putting a . in one's PATH. Seems most Linux > >people do indeed put the . in there. *sigh* > > > >-- > >Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl > >The BSD Programmer's Documentation Project > >Network/Security Specialist BSD: Technical excellence at its best > >Whispering winds in moonlit wood, a totem oak once golden stood... > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message