Re: tricky shell script question

2008-02-12 Thread Paul Jarc
"Erik-Jan Taal" <[EMAIL PROTECTED]> wrote: > Now watch the terminal where the script was still running. I would > expect no output to be given, as I assumed the script is read into memory > at startup and not during execution and this is what happens on most > systems. On one server however, the '

tricky shell script question

2008-02-12 Thread Erik-Jan Taal
Hello, Anyone know the answer to this? Suppose the following scenario: Edit new file 'p.sh' in vim. Add these lines : #!/bin/sh sleep 30 Now save the file in vim with ':w' and chmod +x it. Then open another terminal and run the script. While that's sleeping, quickly add the following line to

Re: Bash 3.2.25 not expanding subscript...

2008-02-12 Thread Brad Diggs
Bernd, Thank you so very much!!! I would have never figured that out on my own. I went back to the Advanced Bash Scripting Guide (by Mendel Cooper) to see if this example would make a good addition. Searching on your use of Here Strings (e.g. <<<). I found on page 326 (18.1. Here Strings) a

Re: Bash 3.2.25 not expanding subscript...

2008-02-12 Thread Bernd Eggink
Brad Diggs schrieb: In short the bug is the result of failure to expand the subscript of an array if the subscript is a variable. The following script should return a list of files with a preceding (File <#>: ). However, it does not work that way because the integer variable (${d}) used in th