On 1/28/10 3:55 AM, Dan Zwell wrote:
> Bash Version: 4.1
> Patch Level: 2
> Release Status: release
>
> Description:
> When I attempt to run an alias, Bash occasionally says the command
> is not found. Re-running the command generally succeeds. This also
> occurs with aliases that are named after existing programs. For example,
> running "ls", which is aliased to "ls --color", occasionally results in
> "ls" being run without the "--color" argument (the alias is bypassed).
>
> Repeat-By:
> This problem seems to occur once every few hundred aliased commands
> I run. It seems more frequent immediately after sourcing a .bashrc file.
> I cannot reproduce it with a loop that repeatedly runs an aliased command.
>
> Is this a known issue? I may be able to help debug this (perhaps by
> modifying my build to log state when a command is not found).
This is not a known issue. If you can provide me a way to reliably
reproduce it, then I can look at a possible problem and fix.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
