Mail Archives: cygwin/1998/09/05/21:13:33
In article <35EFD8AE DOT 856648C4 DOT cygnus DOT gnu-win32 AT harlequin DOT co DOT uk>,
Schzen Ooi <io AT harlequin DOT co DOT uk> wrote:
>Suppose, you had a script in, say, "d:/usr/local/bin/which" is defined
>as:
>
>>#!/bin/sh
>>OFS=$IFS
>>IFS=:
>>for p in $PATH; do
>> if [ -f "$p/$1" ]; then
>> ls "$p/$1"
>> exit 0
>> fi
>>done
>>IFS=$OIFS
>>
>>#type -p $1
>
>to demonstrate the output below, and running it [might] give the
>following results:
>
>>bash2$ whereis ls
>>/usr/H-i386-cygwin32/bin/ls
>>//d/usr/local/bin/whereis: waitforjob: no children
>>bash2$
>
>Changing the "#!/bin/sh" to "#!/usr/local/bin/bash" makes the message go
>away,
>I have the following in d:/bin/sh.exe,
>d:/usr/H-i386-cygwin32/bin/bash.exe
>and d:/usr/local/bin/bash.exe for convenience and they are just
>duplicates.
>
>and mount paths defined with
>"d:\usr\H-i386-cygwin32\bin" -> "/bin"
>"d:\usr" -> "/usr"
>if this detail is significant.
>
>What does the waitforjob mean?
It usually means that ash is confused by pids > 32767. Try running a coolview
version of the .dll: http://www.lexa.ru/sos .
--
cgf AT cygnus DOT com "Everything has a boolean value, if you stand
http://www.cygnus.com/ far enough away from it." -- Galena Alyson Canada
- Raw text -