Tip of the day - USER command

[Jerry Rains]

On Friday 19 March 2004 23:01, Kenneth Brody wrote:
> 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.
> > Bob Stockler wrote:
> > What it you moved it to another name and wrote a shell
> > script wrapper for it where you trapped the INT signal ???
> Ken Brody wrote:
> filePro already starts the user program with SIGINT disabled.  If pressing
> break exits the program, it means that it is explicitly re-enabling it.

That's interesting.   All I know is if I don't touch Break then the program 
doesn't crash, if I do it does.  Somehow Break is getting through.  I guess 
I'm going to have to learn more about how 'netcat' works.

Jerry