Re: ksh - issue with (non-existing) jobs

On 26.01.2025 22:58, Lawrence D'Oliveiro wrote:

On Sun, 26 Jan 2025 13:13:37 +0100, Janis Papanagnou wrote:
 

You initiate jobs, say, by something like 'a_command &', the command
gets registered in a shell table. And at any time you can 'wait' for it.

 
The “wait” command doesn’t require you to specify which job to wait for.

Yes, so what? - Mind that there's no process/job running any more.

If you don't name any specific job, what will that then lead to in
case there's no job to wait for, but still job entries in the shell
internal jobs-table? If there's no signal or information that the
shell can get active on? - I'm not sure what you think to be gained
then by a call of 'wait' (without arguments).

I think it's a shell internal job-table maintenance problem; since
it says (in case of 'kill') "no such job" but still show them with
the 'jobs' command.

I'm anyway just curious how that inconsistent state might have got
created. - And whether there's some indication of a bug that could
get fixed.

Janis