SCO idleout time causing lockfile problems?

[Mike Schwartz]

     On SCO Openserver 5.0.6 with filePro 5.6, would the SCO idleout command
be causing them any file locking or other difficulties?

 

       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.

 

     I'm going to try and talk them into lengthening the timeout to 90
minutes.  All they really need to do is make sure everybody is out of the
files before the 11:00 PM tale backup kicks in. 

 

Thanks!

 

Mike Schwartz

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20120327/1346e2b3/attachment.html