From owner-freebsd-bugs Tue Nov 7 06:41:32 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA20377 for bugs-outgoing; Tue, 7 Nov 1995 06:41:32 -0800 Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id GAA20367 for ; Tue, 7 Nov 1995 06:41:26 -0800 Received: by Sysiphos id AA15411 (5.67b/IDA-1.5 for bugs@freebsd.org); Tue, 7 Nov 1995 15:40:30 +0100 Message-Id: <199511071440.AA15411@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 7 Nov 1995 15:40:29 +0100 In-Reply-To: "Petr Kodl" "/bin/csh" (Nov 7, 15:17) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: pecold@abrcp.cz Subject: Re: /bin/csh Sender: owner-bugs@FreeBSD.org Precedence: bulk On Nov 7, 15:17, "Petr Kodl" wrote: } Subject: /bin/csh } It seems there is a bug in /bin/csh in 2.0.5 release. It sometimes } doesn't recognize executables on path (except . ). It happenes, when the } executable is added or created while csh is already running. If I } want the csh to recognize the new executable file, I have to set path } or run new csh, which is not very comfortable. Does anybody know } better solution. Well, that's not a bug, it's a feature :-) In fact, the csh uses a cache of paths to executables, and if you install a new one, you are expected to use the "rehash" builtin command, to re-initialise the cache ... (Changing the PATH does this as a side effect.) See the csh man page. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se