rreport gagging on lockfile

[Ken Cole]

Tyler,

I would like to revisit what someone else suggested very early on in
this thread.

I suspect the lockfile is being left by a crashing application or
someone crashing out/breaking out of an application.

Since you say you are running this on Linux I guess your users are
using a terminal emulator to access the filePro apps.  This sort of
thing can happen if a users PC reboots while they are in filePro or
they close the emulator while apps are running, etc.

We eliminated the "closing the emulator when they shouldn't" by using
AnzioLite's kiosk mode which removes the capability to click the X in
the top right of the window and also removes the File->Exit command.
We setup AnzioLite to close down on logout.

This helped us with similar issues many many moons ago.

Do you have any new users who may not understand how the emulator
works and that closing it while apps is running is a "bad thing"?

Cheers

Ken

On Thu, Feb 4, 2010 at 9:27 AM, Tyler <tyler.style at gmail.com> wrote:
> Well, spoke too soon.  The problem recurred just now.  Here is the error
> message:
>
>
>
> *** A filePro Error Has Occurred ***
>
> On File: /hd1/hd1/appl/filepro/log_operations/lockfile
>
> Request Output with Processing Function Running On This File
>
> File not available.
> Somebody else is modifying the file;  try again later.
>
>
>
> Deleting the lockfile allowed things to go forward smoothly.  Does this
> provide anyone with any fresh insights?
>
> Tyler
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>