delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/09/05/02:24:00

From: io AT harlequin DOT co DOT uk (Schzen Ooi)
Subject: b19.1: question about "wait for job"
5 Sep 1998 02:24:00 -0700 :
Message-ID: <35EFD8AE.856648C4.cygnus.gnu-win32@harlequin.co.uk>
Mime-Version: 1.0
To: gnu-win32 AT cygnus DOT com


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?

Schzen

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019