Sujet : Re: When/why does the shell (bash) (sometimes) not re-cycle job IDs?
De : gazelle (at) *nospam* shell.xmission.com (Kenny McCormack)
Groupes : comp.unix.shellDate : 12. May 2024, 03:30:29
Autres entêtes
Organisation : The official candy of the new Millennium
Message-ID : <v1p9k5$s8og$2@news.xmission.com>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
In article <
v1p6hr$2btq7$1@dont-email.me>,
Janis Papanagnou <janis_papanagnou+
ng@hotmail.com> wrote:
On 12.05.2024 02:14, Lawrence D'Oliveiro wrote:
On Sat, 11 May 2024 22:44:03 -0000 (UTC), Christian Weisgerber wrote:
If no job is running, a new job gets 1, otherwise new jobs are numbered
consecutively.
Job numbers are reused after it has notified you of termination of the
previous job. At least in Bash.
>
Also the same behavior in Ksh, ever since I can remember; lowest job
number "available" gets re-used first. (Where "available" means that
its finishing status has been reported and not that the job finished.)
Nope. Sorry.
-- Those on the right constantly remind us that America is not ademocracy; now they claim that Obama is a threat to democracy.
When/why does the shell (bash) (sometimes) not re-cycle job IDs?
Re: When/why does the shell (bash) (sometimes) not re-cycle job IDs?