SCO idleout time causing lockfile problems?

[Jean-Pierre A. Radley]

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'.

| 
| >         The idleout is set to 60 right now  (60 minutes).  I want to tell the
| > users to be sure *not* to  leave their filepro sessions in update mode on a
| > record when they go to lunch or attend a lengthy meeting, but is there
| > really any possibility of corrupt records or lockfile problems if idleout
| > kicks in while their screens are in update mode?  Does idleout do a "clean"
| > closing of any application that is running on their terminals?  I have
| > already told them that any information that they had updated on any open
| > screens would be lost if they haven't pressed esc-esc yet.
| [...]
| 
| -- 
| Kenneth Brody
| _______________________________________________
| Filepro-list mailing list
| Filepro-list at lists.celestial.com
| Subscribe/Unsubscribe/Subscription Changes
| http://mailman.celestial.com/mailman/listinfo/filepro-list

-- 
JP