SCO idleout time causing lockfile problems?

[Mike Schwartz]

> On 3/27/2012 3:14 PM, Jean-Pierre A. Radley wrote:
> > Kenneth Brody propounded (on Tue, Mar 27, 2012 at 11:10:02AM -0400):
> > | On 3/27/2012 7:40 AM, Mike Schwartz wrote:
> > |>        On SCO Openserver 5.0.6 with filePro 5.6, would the SCO
> > |> idleout command  be causing them any file locking or other
difficulties?
> > |
> > | It depends.  What signal does it use to kill idle programs?
> >
> >
> > On a 5.0.7 machine, idleout (which is a shell script) carries a date
> > of 1996; I imagine the 5,0,5 version was pretty much the same.  A
> > 'grep kill' command turns up several instances, all of them 'kill -9'.
> [...]
> 
> In that case, there's your answer.  It is not possible to catch a "kill
-9"
> signal, so filePro cannot clean up on the way out.
> 
> --
> Kenneth Brody

     Ok, thanks, Ken!  I was afraid that might be the case, but it is the
answer I was looking for.

     Thanks to JP, too!  Maybe I can modify the shell script to try a
different level of kill. 

     I did adjust the idleout to 90 minutes instead of 60 minutes, so that I
don't get so many kills during lunch hour and during lengthy meetings.
However, the easiest thing to do at night, which Dan suggested, will
probably be to turn off idleout before they launch the nightly batch
repiorts and tape backup scripts, then turn it back on after everything
finishes. 

Mike Schwartz