Hello,
We are experiencing an unusual problem. First of all we have a 4100 Alpha
servers running 4.0D PK3. We have an AdvFS called /projects and developers
working on projects in this directory like to add directories to their $PATH
to test commands. The problem occurs a when new command is added to one of
these directories. When the developer logs in everything works as expected,
and commands in the PATH are found and run. But when a new command is
created in a directory in the PATH you recieve the error:
<new_cmd>: not found.
If they have the "." in their PATH and <new-cmd> is in the current
directory, they can run new commands, but if they are outside the directory
where <new_cmd> was created it will not be found.
If you log out then log back in the <new_cmd> will be found and everything
will work normally again. They are in the "tcsh" shell and running "setenv
PATH $PATH" will also resolve the problem and we can see the new commands.
However, this is an annoying work around, and if you add another new
command, you have to do it again.
Has anybody ever seen this? I'm a ksh guy and have never experienced this
before, could this be a tcsh thing? It almost like command listings in the
PATH are stored in a buffer somewhere and you can't find new commands until
the buffer is updated.
Jim Fitzmaurice
jpfitz_at_fnal.gov
UNIX is very user friendly, It's just very particular about who it makes
friends with.
Received on Thu Oct 21 1999 - 19:01:00 NZDT