From owner-freebsd-questions@FreeBSD.ORG Fri Feb 2 06:05:55 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5EA8316A400 for ; Fri, 2 Feb 2007 06:05:55 +0000 (UTC) (envelope-from bsdaemon@comcast.net) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [204.127.192.82]) by mx1.freebsd.org (Postfix) with ESMTP id 396FF13C46B for ; Fri, 2 Feb 2007 06:05:55 +0000 (UTC) (envelope-from bsdaemon@comcast.net) Received: from fw.home (c-68-39-195-31.hsd1.pa.comcast.net[68.39.195.31]) by comcast.net (rwcrmhc12) with SMTP id <20070202060554m1200rat1ne>; Fri, 2 Feb 2007 06:05:54 +0000 Received: (qmail 8559 invoked by uid 1003); 2 Feb 2007 06:05:53 -0000 Date: Fri, 2 Feb 2007 01:05:53 -0500 From: Kris Maglione To: freebsd-questions@freebsd.org Message-ID: <20070202060553.GA7806@fw.home> Mail-Followup-To: freebsd-questions@freebsd.org, Gobbledegeek References: <463aea570702012137m48215342of428b69a18641c71@mail.gmail.com> <20070202055729.GA7303@fw.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20070202055729.GA7303@fw.home> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Gobbledegeek Subject: Re: windows behaviour on installing new packages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2007 06:05:55 -0000 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?