Tip of the day - USER command

[Kenneth Brody]

Bob Stockler wrote:
[...]
> | > > I've been working with the USER command a lot recently and was having
> | > > problems with it either hanging or blowing up.  I determined that if the
> | > > user presses Break just before the USER command was written to, it
> | caused
> | > > filePro to exit to the shell.
> | > Ken Brody wrote:
> | >
> | > Only if your USER program exits when break is pressed.
> |
> | That's the problem.  It does, but it isn't my program and I don't have the
> | source code so I can't fix it.
> 
> What it you moved it to another name and wrote a shell
> script wrapper for it where you trapped the INT signal ???

filePro already starts the user program with SIGINT disabled.  If pressing
break exits the program, it means that it is explicitly re-enabling it.

-- 

+---------+----------------------------------+-----------------------------+
| Kenneth |     kenbrody at spamcop.net      | "The opinions expressed     |
|    J.   |    http://www.hvcomputer.com     |  herein are not necessarily |
|  Brody  |      http://www.fptech.com       |  those of fP Technologies." |
+---------+----------------------------------+-----------------------------+