Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!husc6!speed!bochner
From: bochner@speed.harvard.EDU (Harry Bochner)
Newsgroups: comp.databases
Subject: Hang-up signals in Informix 4gl
Message-ID: <2536@husc6.harvard.edu>
Date: 11 Apr 90 17:34:45 GMT
Sender: news@husc6.harvard.edu
Reply-To: bochner@harvard.EDU (Harry Bochner)
Organization: Aiken Computation Laboratory, Harvard University
Lines: 20

I've been having the following problem with INFORMIX-4gl RDS (2.10.03F
on a sun4):
Our users use rlogin from (Encore) annex boxes. From time to time a user is
forceably logged out, for instance because of a failure in the annex
box. The host
machine gets a hangup signal, which properly kills the login shell, but it
doesn't kill the user's 4gl processes: instead of dying, fglgo falls
into a tight
loop (probably trying to report the error?), and eats up all the CPU
time it can
grab. These runaway jobs keep running, and degrading system performance, until
they are killed manually (or the system crashes).

I figure I can probably write an interrupt handler in C, or perhaps just set
the handler for the hangup signal to be the same as the one for interrupt, but
I've been trying to minimize the amount of C code I use, so I'm wondering if
anyone can suggest another solution.

Harry Bochner
bochner@endor.harvard.edu