Charles
you wrote
>Keep track of the process ID of the spawned CGI script, and
>watch in
>/proc
>for the process directory to
>disappear...something like
>
>$LOCALURL "$@" > $OUTPUT &
>CGI_PID=$!
>CNT=1
>while [ -e "/proc/$CGI_PID" ] ; do
> ...
>done
This could work, but it waits for only one background proces.
>
> > $LOCALURL "$@" >$OUTPUT &
> > while [ -n "`jobs`" ];do
> > .
> > sleep 1
> > done
> >
> > This works under Eigerstein but with the "other" ash
> > "`jobs`" doesn't function
> > I tried [ -n `jobs` ] among a lot others but this loops forever (actuall
> > stopped by an other loop counter)
>
> Sounds like "job support" isn't in Oxygen ash...
jobs on the command line functions if I have a background process
running
I wrote testprogram
nc 192.168.1.1 11 & (just to create a background program)
CNT=1;
while [ -n `jobs`]
do
jobs
CNT=`expr $CNT + 1`
if [ $CNT -eq 100 ]
then
echo "ben bij honderd"
exit 0
fi
done
this prints
[1] 24200
...
...
[1] 24200
nc: connect: No route to host
[1] 24200 Exit 1
ben bij honderd
if I change the line
jobs
to
jobs >>/tmp/iets
then iets contains
60 lines with [1] 21244
but
jobs | wc
shows
60 lines with 0 0 0
So I seem to have a problem with pipes could that be busybox ?
I still use your 0.50
>
> > Has someone a suggestion how I could change this.
> > the result should be :
> >
> > loop until the background jobs are finished
> > then continue.
>
> Sounds like:
>
> wait
you caught me again with not enough information ;)
this loop can also be stopped it it takes to long so a timeout occurs
wait would wait for the background proces to finish. even if it didn't
finish ?
>
> ...to me.
>
> About the busybox fix: they improved my patch and put it into CVS....
Very Good.
I post another busybox question in the next post.
Thanks again
Eric Wolzak
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
