Re: Is it possible to timeout 4GL?

> From: paulw@dev.jcdc.eta.gov > Date: Wed, 13 Jul 1994 14:48:40 -0500 (CDT) > > We had this problem before also on our AIX box, but rather that look to code > to fix the problem, we used our UNIX knowledge. > > In the users .profile files, rather than just fglgo'ing the program, we > exec fglgo the program. This lets the kill signals get to through when > a user disconnects abruptly. > > If this is not acceptable, another solution is to write a shell script that > kill process that have been sitting for X number of minutes, using the > who -u command to provide the list of inactive users. Then running the > script every so often using cron. While this can be a valid method of removing stale processes, be aware that there are times when the 4GL process can be sitting idle for LONG period, while the sqlturbo/sqlexec is off in the background crunching away. Notably on large queries against lots of data. To the system, it will look as if the 4GL is just sitting idle and a candidate for being a rogue process, when in fact it isn't. So, if you're going to implement this kind of procedure, be sure that you look at all of the users processes, and not just the 4GL. Will (villy@collinscomp.com)