rreport gagging on lockfile

[Kenneth Brody]

On 2/1/2010 1:47 PM, Tyler wrote:
> We suddenly started having a problem a week ago with a piece of logging
> software that has run perfectly for years.  Every time a script or
> processing ran that used it, it would bomb out with a message that the file
> was locked by output processing.
>
> After some hemming and hawing, it was determined that the lockfile status
> wasn't being read correctly.

What do you mean by "the lockfile status wasn't being read correctly"?

> rreport was hung on the lockfile message,

What was the exact message?

> and
> trying to access it via rclerk kicked you immediately with the same
> message.  However, the lockfile script showed that the file wasn't actually
> locked.

What "lockfile script"?

> We manually deleted the lockfile and re-ran a report that had been
> previously gagging so that filepro (v5.0.1.14 on SCO Openserver 6) could
> recreate it.  Suddenly everything is fine.
>
> Anyone have any ideas on why this would have happened, and how we might
> avoid it in the future?  Thanks for any input!

Is this a consistent problem?  Or was it just something like a previous 
*clerk session had crashed?

-- 
Kenneth Brody