correction, for logs: My first conclusion that "sh(1) reads file in process of execution" was wrong. Looks like when file size is increasing during script execution, sh(1) additionally executes file "tail" (starting at old EOF seek position). I guess, this behavior is useless (and dangerous) for regular files. When file size decreasing or does not changing, nothing is happening.
IAK> I found out that sh(1) reads file in process of execution (instead of IAK> read whole file and execute it from memory image), which makes IAK> editing such scripts unreliable and/or dangerous. Is there any IAK> existing ways to solve this problem ? IAK> Is there sense to make sh(1) to read whole script file before IAK> executing (optionally, at least), because, as far as I understand, IAK> current behavior is pretty useless as feature ? Ilya A. Kovalenko (mailto:[EMAIL PROTECTED]) Special EQ SW section JSC Oganer-Service
