<br><br><div class="gmail_quote">On Tue, Mar 27, 2012 at 7:40 AM, Mike Schwartz <span dir="ltr"><<a href="mailto:mschw@athenet.net">mschw@athenet.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On SCO Openserver 5.0.6 with filePro 5.6, would the SCO idleout command<br>
be causing them any file locking or other difficulties?<br>
<br>
<br>
<br>
The idleout is set to 60 right now (60 minutes). I want to tell the<br>
users to be sure *not* to leave their filepro sessions in update mode on a<br>
record when they go to lunch or attend a lengthy meeting, but is there<br>
really any possibility of corrupt records or lockfile problems if idleout<br>
kicks in while their screens are in update mode? Does idleout do a "clean"<br>
closing of any application that is running on their terminals? I have<br>
already told them that any information that they had updated on any open<br>
screens would be lost if they haven't pressed esc-esc yet.<br>
<br>
<br>
<br>
I'm going to try and talk them into lengthening the timeout to 90<br>
minutes. All they really need to do is make sure everybody is out of the<br>
files before the 11:00 PM tale backup kicks in.<br>
<br>
<br>
<br>
Thanks!<br>
<br>
<br>
<br>
Mike Schwartz<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://mailman.celestial.com/pipermail/filepro-list/attachments/20120327/1346e2b3/attachment.html" target="_blank">http://mailman.celestial.com/pipermail/filepro-list/attachments/20120327/1346e2b3/attachment.html</a><br>
_______________________________________________<br>
Filepro-list mailing list<br>
<a href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a><br>
Subscribe/Unsubscribe/Subscription Changes<br>
<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
</blockquote></div><br>You could also set cron to turn idleout on every night at 10PM (and off after your backup completes). That way your backup would be clean and you wouldn't have to worry about somebody taking a long lunch and forgetting to finish saving a record. Only the more careless users that left work w/o logging out properly might have their work affected. <br clear="all">
<div><br></div>-- <br>daN baueR<br><a href="mailto:dan@onlinemgt.com">dan@onlinemgt.com</a><br>google voice 347-542-7267<br>