Firstly as a minor nit that seems to re-appear yearly there are still
source files in the release tarballs that are not readable to a normal
user :
#
# find . -ls | grep '\-\-\-'
7348095 24 -rw--- 1 286 staff 38962 Jul 8 14:19 ./lib/malloc/malloc.c
73474421 -rw--- 1 286 staff 22
Date:Tue, 29 Dec 2020 10:23:07 -0500
From:Chet Ramey
Message-ID:
| Bash will save some number of exit statuses corresponding to terminated
| asynchronous child processes, and those statuses are retrievable using
| `wait'. That number varies -- POSIX says you ne
On 12/29/20 10:28 AM, Chet Ramey wrote:
On 12/28/20 5:30 PM, Eli Schwartz wrote:
(Though I have to wonder at these amazing AWOL commands that get
uninstalled on people all the time right in the middle of their scripts.
It's a potential security concern, though that class of vulnerabilities
m
On 12/27/20 11:29 PM, William Park wrote:
I have feature request: stack variable. Almost like current DIRSTACK
with 'pushd' and 'popd', but for regular arrays.
I know it can be implemented with array, where you push and pop from the
end. But, a real stack is better.
How is putting something
On 12/28/20 5:30 PM, Eli Schwartz wrote:
(Though I have to wonder at these amazing AWOL commands that get
uninstalled on people all the time right in the middle of their scripts.
It's a potential security concern, though that class of vulnerabilities
mostly involves executables being changed
On 12/28/20 1:23 AM, Markus Elfring wrote:
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 handl
>…, is not a winning argument.
I got further development ideas according to the usage of wait function calls
and better error reporting for asynchronous commands.
>The OP seems to think that "people will occasionally forget to run `wait`",
This happens for various reasons.
> and wants to know
