rreport gagging on lockfile

[Tyler]

No, definitely not the case.  We have 5.6 but still haven't finished
testing/updating our processing on our test box.

On Mon, Feb 1, 2010 at 1:02 PM, John Esak <john at valar.com> wrote:

>  Any chance you are working with 5.6 filePro and once accessed a
> non-locked file with a pre-5.6 version of one of the runtimes?   This would
> create a lockfile problem for 5.6.  They do not commingle backwards.
>
> John
>
>
>  ------------------------------
> *From:* filepro-list-bounces+john=valar.com at lists.celestial.com [mailto:
> filepro-list-bounces+john <filepro-list-bounces%2Bjohn>=valar.com@
> lists.celestial.com] *On Behalf Of *Tyler
> *Sent:* Monday, February 01, 2010 1:48 PM
> *To:* filepro-list at lists.celestial.com
> *Subject:* rreport gagging on lockfile
>
> 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. rreport was hung on the lockfile 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.
>
> 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!
>
> Tyler
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20100201/71d43dce/attachment.html