b19.1: question about "wait for job"

Christopher G. Faylor cgf@cygnus.com
Sat Sep 5 18:37:00 GMT 1998

In article <35EFD8AE.856648C4.cygnus.gnu-win32@harlequin.co.uk>,
Schzen Ooi <io@harlequin.co.uk> wrote:
>Suppose, you had a script in, say, "d:/usr/local/bin/which" is defined
>>for p in $PATH; do
>>  if [ -f "$p/$1" ]; then
>>    ls "$p/$1"
>>    exit 0
>>  fi
>>#type -p $1
>to demonstrate the output below, and running it [might] give the
>following results:
>>bash2$ whereis ls
>>//d/usr/local/bin/whereis: waitforjob: no children
>Changing the "#!/bin/sh" to "#!/usr/local/bin/bash" makes the message go
>I have the following in d:/bin/sh.exe,
>and d:/usr/local/bin/bash.exe for convenience and they are just
>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@cygnus.com             "Everything has a boolean value, if you stand
http://www.cygnus.com/      far enough away from it."  -- Galena Alyson Canada
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

More information about the Cygwin mailing list