Re: Checking executability for asynchronous commands

[Markus Elfring]

> If you have the pid of an asynchronous command -- and the easiest way to get 
> that pid
> is by referencing $! after it was started -- you can call `wait' with that pid
> to retrieve the status, even if it's already terminated.

Would you care if waiting on such identifications for background processes
will occasionally be forgotten?

How many efforts would you invest to add potentially missing wait function 
calls?

Regards,
Markus