Interprocess communication and the USER call

[Kenneth Brody]

Quoting Tom Pancero (Thu, 26 May 2005 08:04:20 -0400):
[... filePro closing the USER program ...]
> I am using the SIGNAL() function, in C, to handle a <CTL>C if the
> interface is invoked from the command line (Debug).  I wish to find out
> the specific IP_Signal that the interface will receive when the USER
> call is terminated by the Filepro processing completing its run.
>
> I know that sending a <CTL>C generated a SIGINT signal.

Please don't exit on SIGINT when not in debug mode, as your program
will exit before filePro tells it to.  (ie: if the user presses BREAK
to exit update mode in filePro, your program will exit when it
shouldn't.)

> Filepro, apparently, does not send a SIGINT signal. Nor does
> it seem to send a SIGHUP or a SIGQUIT.

The user hasn't hung up (hence, no SIGHUP), nor has the user pressed
ctrl-\ (hence, no SIGQUIT).

> Can someone shed some light on this for me?
[...]

filePro sends no signals to the USER program.  It will, however,
close the pipe between it and you, causing you to read EOF on
stdin.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com