Sorry Walter,

I really wanted to be able to solve this problem but TurboIMAGE itself
is the party pooper. Those unconditional locks will hang you up
every time, regardless of whether you are the parent or child process.

Yes, I think I had said something earlier on that locking shouldn't be done 
around terminal reads. Do the locking AFTER the user presses the enter key
(or function key).

I think I have more chance of winning the lottery than there is of HP
giving us the solution to this problem.

Good Luck, Walter.


Brian.
On Thu, 5 Jun 2008 21:50:33 -0700, Walter J. Murray <[log in to unmask]>
wrote:

>Dave wrote,
>
>> Looks like Walter's best approach is to hunt down the apps that lock
>> around terminal I/O, like others suggested before.
>
>I agree.
>
>I'm astounded at how much interest this topic has generated.  Thanks to
>all for your suggestions, and especially to Brian for the time he has
>invested trying things out.
>
>I'm surprised HP didn't implement timed lock requests years ago.  I've
>decided to wait until they introduce this in a future release of
>TurboIMAGE.  :-)
>
>Walter
>
>Walter J. Murray
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *