Date:Thu, 13 Sep 2018 17:22:46 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20180913152246.gm5...@trav.math.uni-bonn.de>
| > You're using an old version, not NetBSD current (or 8) right?
| 6.1, mostly (for the ash part), yes.
The jobs command implementatio
> You're using an old version, not NetBSD current (or 8) right?
6.1, mostly (for the ash part), yes.
> and now the only way for a script to make a job vanish from the
> jobs table (and so, from being seen in the output of jobs -p) is
> to "wait" for it.
Surely you've digested what SUS says about t
> You mean xargs -p, essentially?
xargs -L 1 -P (capital) would have done the job if
a) had I known about it (thanks for the hint!)
b) it were POSIX
Date:Thu, 13 Sep 2018 14:00:10 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20180913120009.ge5...@trav.math.uni-bonn.de>
| is the job then supposed to show up in "jobs -p" output?
| In bash, at least for a), the job does show up until you call jobs without
On Thu, Sep 13, 2018 at 02:00:10PM +0200, Edgar Fuß wrote:
> The objective was to write s shell script that parallelized invocations of
> some command, but only up to a certain number of jobs running in parallel.
> There were two ideas to implement this, one using the jobs utility to track
> the
I could probably as well directly mail kre@, but who knows.
The objective was to write s shell script that parallelized invocations of
some command, but only up to a certain number of jobs running in parallel.
There were two ideas to implement this, one using the jobs utility to track
the curren
