In this case, the problem is in how you deploy the scripts, and not
with bash. Don't change a running script, just write the new script
to a temp file and then replace the script.
That looks something like this:
mv newscript oldscript
This way, bash will keep reading from oldscript, but new in
"Aronesty, Erik" writes:
> I'd like to add a very simple command line flag to bash that forces it to
> make a temporary copy of the script that's running so that developers of
> scripts in these environments can continue to use tools like rsync or git,
Neither rsync nor git update files in-place
