Odd shell -- or shell script -- behavior
by rnturn from LinuxQuestions.org on (#4VY2G)
I've been writing code for a long time but I can't say that I've ever encountered this until today...
I have a bash script that reads large datasets and extracts information out to a files that I'll be converting to a different format later. I kicked off the script a while ago and, while it was running, decided to edit the script and add
Code: mplayer -quiet read.wav completed.wavto the very end so I would know when it was done. (It can take maybe 10 minutes to run so I'll multitask while it's grinding away.) At least, I thought, on the next run I'd get an audible indication that it was done and I could go on to the next run.
The weird thing is that the audible announcement came at the end of the run that was in progress -- and not yet completed -- when I finished with the edit to the script.
I would expected that the run in progress would complete silently and that the mplayer line would not have been "seen" until the next time the script was run.
Has anyone else noticed this?
The seems to be a new behavior. It looks like I'll need to be careful when making edits from here on.
I have a bash script that reads large datasets and extracts information out to a files that I'll be converting to a different format later. I kicked off the script a while ago and, while it was running, decided to edit the script and add
Code: mplayer -quiet read.wav completed.wavto the very end so I would know when it was done. (It can take maybe 10 minutes to run so I'll multitask while it's grinding away.) At least, I thought, on the next run I'd get an audible indication that it was done and I could go on to the next run.
The weird thing is that the audible announcement came at the end of the run that was in progress -- and not yet completed -- when I finished with the edit to the script.
I would expected that the run in progress would complete silently and that the mplayer line would not have been "seen" until the next time the script was run.
Has anyone else noticed this?
The seems to be a new behavior. It looks like I'll need to be careful when making edits from here on.