records not locking?

[scooter6 at gmail.com]

I'll have to dig thru the code and see  - there are several 'writes' in the
processing, but every subsequent lookup is protected.....
As for copying the files, I didn't copy ANY filepro files when we had the
root kit issue - it was JUST the OS -- so I can't see that being the issue
We don't have the PFREADONLY flag set at all, not in configuration editor
and not in anyone's profile....


On Wed, Apr 16, 2014 at 12:21 PM, Kenneth Brody <kenbrody at spamcop.net>wrote:

> On 4/16/2014 11:35 AM, scooter6 at gmail.com wrote:
>
>> So in looking at the fp.log file in /tmp -- I can see we've had these type
>> messages since day 1 so not sure how this plays into it
>> \r WARNING \r Assigning to lookup field without lock.
>> mainfile=NRcollect, loofile=NRdebtor, prc=input, line=664
>> \r WARNING \r Assigning to lookup field without lock.
>> mainfile=NRcollect, loofile=NRdebtor, prc=input, line=497
>> \r WARNING \r Assigning to lookup field without lock.
>> mainfile=NRcollect, loofile=NRdebtor, prc=input, line=498
>>
>> But these lines aren't gotten to until after the lookup is done and it's a
>> protected lookup...so not sure what is happening here...or if it's even
>> related, since it appears we've gotten these lines for a really long
>> time.....
>>
>
> Do you WRITE the record after the lookup, but prior to executing those
> lines?
>
> --
> Kenneth Brody
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20140416/0b79598a/attachment.html