On Sat, Jan 05, 2019 at 08:28:45AM +, Paulo Nogueira wrote:
> What occurred to me is the following: suppose a script s1 starts
> being executed, by forking say, and then s1 is overwritten
DON'T... DO... THAT.
Problem solved.
On 1/5/19 3:28 AM, Paulo Nogueira wrote:
> What occurred to me is the following: suppose a script s1 starts
> being executed, by forking say, and then s1 is overwritten; bash
> detects this and re-reads the file.
Bash doesn't do that.
> OK, then exactly where does
> bash continue executing
On Sat, 29 Dec 2018, Chet Ramey wrote:
http://lists.gnu.org/archive/html/bug-bash/2018-09/msg00023.html
Not sure if I understood everything, so allow me to quote you,
from
http://lists.gnu.org/archive/html/bug-bash/2018-09/msg00024.html
... It's been there
even since I wrote the buf
On 12/29/18 6:09 AM, Paulo Nogueira wrote:
>
>
> Bash Version: 4.4
> Patch Level: 19
> Release Status: release
>
> Description:
>
> I've come to the conclusion that bash scripts
>
> (1) are not entirely loaded in memory at once
>
> or, at least,
>
> (2) are re-read (from the disk?) if th
Bash Version: 4.4
Patch Level: 19
Release Status: release
Configuration Information:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Description:
I've come to the conclusion that bash scripts
(1) are not entirely loaded in memory at once
or, at least,
(2) are re-read (from the disk?) i
