Date: Fri, 2 Feb 2007 13:21:34 +0530 From: Gobbledegeek <gobbledegeek@gmail.com> To: freebsd-questions@freebsd.org, Gobbledegeek <gobbledegeek@gmail.com> Subject: Re: windows behaviour on installing new packages Message-ID: <463aea570702012351m771c0cdfh12d60118eab1b01b@mail.gmail.com> In-Reply-To: <20070202060553.GA7806@fw.home> References: <463aea570702012137m48215342of428b69a18641c71@mail.gmail.com> <20070202055729.GA7303@fw.home> <20070202060553.GA7806@fw.home>
next in thread | previous in thread | raw e-mail | index | archive | help
yes yes yes yes to all... thanks for the tip about the rehash and csh behaviour though. Regards On 2/2/07, Kris Maglione <bsdaemon@comcast.net> wrote: > On Fri, Feb 02, 2007 at 12:57:29AM -0500, Kris Maglione wrote: > >On Fri, Feb 02, 2007 at 11:07:58AM +0530, Gobbledegeek wrote: > >>I noticed over the past few weeks, that after installing numerous > >>packages (pkg_add -r), I could not execute them (not found). They > >>were standard packages installed in the standard locations like > >>/usr/local/bin or sbin (already in $PATH). Running ldconfig, logging > >>out and logging back in did not help either. *Rebooting* helps > >>however. > > > >The problem is that csh does not recheck your $PATH, but only hashes it > >once. You can get it to rehash by running the aptly named `rehash` > >command, or starting a new shell. ldconfig has nothing to do with > >locating executables. > > Sorry, I missed the part about logging out and back in before. In that > case, this is a strange issue. > > Have you varified that the executables exist and are executable when you > try them? Are you sure that you've typed them correctly? Have you tried > entering the entire paths of the executables? Are any of the executables > scripts with initial shebang (#!) lines, and, if so, do the targets of > the lines exist? > -- Rgrds GobbledeGeek [Everything but Gobbledegook.. !!]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?463aea570702012351m771c0cdfh12d60118eab1b01b>