[NTLUG:Discuss] Command not found
Leroy Tennison
leroy_tennison at prodigy.net
Thu Jan 25 22:16:12 CST 2007
David Stanaway wrote:
> A different approach would be to type:
>
> env
>
>
> at the command prompt, if all looks OK there, edit the script that gives
> the error and add a line near the beginning after any lines that look like:
>
> source /etc/foo/bar
>
> or
>
> . /etc/foo/bar
>
>
> add
>
> env
>
>
> If things look bad there, look at the files referenced in the source or
> . statements, or any assignments to those variables, perhaps the file
> doesn't exist so the script is looking in the wrong place?
>
> You might get more luck describing exactly which scripts you are trying
> to run that give the error, as any system wide corruption of PATH or the
> assignment statement to PATH in /etc/profile will give you much bigger
> probems than running just one isolated script. I would be more inclined
> to suspect that something in the script, or its config files is broken.
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>
>
David's question is exactly what one of mine is: What are you getting
these errors in response to? Post the result of
set | grep PATH
on a line by itself in your next reply so we can see what your path
actually looks like.
Use Ctrl-Alt-F<n> where <n> is a number between about 2 and 6 to get to
an alternate terminal, log in as a different user and see if you get the
same result (determines if this is a system-wide or user-specific problem).
Do you know what that second command is actually supposed to be doing or
is it just a 'mystery message'? When i saw it i thought "What does that
do?"
More information about the Discuss
mailing list