Chet Ramey wrote: > Why? If you're running the script from an interactive shell with job > control enabled, the standard input and standard output will be the > same as the parent shell.
I am kicking myself why I had to be so easily provoked by some posts, as to rewrite the examples as two separate scripts. As originally posted, these are two functions that get called from within the same bash script. Nothing interactive in that. Now, if some other script, that calls my script, were to spin it off with an "&", that's when one of my functions gets stuck there forever. I am trying to find a way for my functions to detect such condition and avoid getting stuck.
