From owner-freebsd-questions Mon Oct 4 11:22:52 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id E2F5F14EFC for ; Mon, 4 Oct 1999 11:22:50 -0700 (PDT) (envelope-from chris@tourneyland.com) Received: from momma ([216.62.177.1]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with SMTP id <0FJ3009T1CE0YZ@mta4.rcsntx.swbell.net> for freebsd-questions@FreeBSD.ORG; Mon, 4 Oct 1999 13:22:49 -0500 (CDT) Date: Mon, 04 Oct 1999 13:21:56 -0500 From: chris@tourneyland.com Subject: Re: 3.3-Release - problem with PATH? In-reply-to: <19991004163708.O63946@daemon.ninth-circle.org> X-Sender: pop992333@mail.9netave.net To: freebsd-questions@FreeBSD.ORG Message-id: <3.0.6.32.19991004132156.008e3850@mail.9netave.net> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Content-type: text/plain; charset="us-ascii" References: <37F7CCFF.D2B7DC70@3-cities.com> <3.0.6.32.19991003122429.008dea80@mail.9netave.net> <37F7CCFF.D2B7DC70@3-cities.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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