[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: problems substituting 'jobs' in a bash script

From: Robert Whent (rwhent)
Subject: RE: problems substituting 'jobs' in a bash script
Date: Fri, 22 Feb 2008 11:40:37 +0100


I really appreciate your rssponse here.

This works !!

However the main issue here is the version of bash I was using which was
GNU bash, version 2.05b.0(4)-release (sparc-sun-solaris2.8)

I was also actually executing on Solaris 10

After installing the latest version of bash, all the problems
disappeared and it does allow you to do things like


even though it was pointed out to me that `jobs` would normally be
expected to run its own shell and therefore fail to see the jobs created
in the parent.

So it looks like that latest version of bash has improved the handling
of the job control quite a bit to make it much more user friendly and
logical !

It would be nice to see some better descriptions in the bug resolution

It looks like I can now use bash to reduce the compile times of my
application by about 48 hours !!!!

Thanks a lot guys



-----Original Message-----
From: Bob Proulx [mailto:address@hidden 
Sent: Friday, February 22, 2008 6:53 AM
To: Robert Whent (rwhent)
Cc: address@hidden
Subject: Re: problems substituting 'jobs' in a bash script

Robert Whent (rwhent) wrote:
> sleep 100 &
> sleep 200 &
> sleep 300 &
> JOBS=`jobs`
> I have also trawled the web and can find no reports of any issues ?

More typically this data would be collected up as you go along.

  sleep 100 &
  JOBS="$JOBS $!"
  sleep 200 &
  JOBS="$JOBS $!"
  sleep 300 &
  JOBS="$JOBS $!"
  echo $JOBS

reply via email to

[Prev in Thread] Current Thread [Next in Thread]