#: 12141 S12/OS9/68000 (OSK)
    09-Sep-91  00:28:08
Sb: #12137-#Intercepts
Fm: BILL HEALTON 73367,357
To: Bob van der Poel 76510,2203 (X)

Bob - I have barely scratched the surface of C programming, but I have worked
with several device drivers. Applying their approach to your problem...maybe
you could try the following:

Create an initial "core" procedure that sets up an intercept, forks the other
procedure(s) of your program and tsleep(0). Then, any signal will wake the
"core" process...which can either ignore it and re-sleep or do your cleanup
and kill the children(ie. your program). The "core" procedure could even be
run at a higher priority than the children to ensure its not pre-empted by
a child during the cleanup/closeout time.

In the above the "core" and children should all be running in User state with
none of the System state restrictions. Hope this is of some help.

Bill Healton 73367,357


There is 1 Reply.