Re: Checking executability for asynchronous commands
From:
Markus Elfring
Subject:
Re: Checking executability for asynchronous commands
Date:
Mon, 28 Dec 2020 07:23:22 +0100
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
>> 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?
>
> It's axiomatic: if you want to make a decision based on the exit status of
> any asynchronous process, you need to use `wait' to obtain the status of
> that process.
>
> I don't think "I don't want to do it that way" is a good reason to provide
> a different method.
I got another programming concern:
Process identifications are a system resource.
The exit status is preserved until this information will eventually be used
for corresponding data processing.
How many processes can a selected system configuration handle?
Regards,
Markus