Subject: Re: b19.1: question about "wait for job"
From: [email-masked] (Christopher G. Faylor)

5 Sep 1998 21:13:33 GMT
Message-ID: <[email-masked]>
References: <[email-masked]>
X-Newsreader: trn 4.0-test63 (15 March 1998)

In article <[email-masked]>,
Schzen Ooi <[email-masked]> 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 .
-- 
[email-masked]             "Everything has a boolean value, if you stand
http://www.cygnus.com/      far enough away from it."  -- Galena Alyson Canada