locked record

[Fairlight]

http://0pointer.de/blog/projects/locking.html

Pretty sure filePro uses fcntl() for record locking.  I know of no other
byte-range locking mechanism.  Which explains -much-, actually, if you read
the article.

Ignore the fool's summation at the end which states file locking in Linux
is unusable.  He's an idiot.  But his technical grounds are sound enough,
even if his conclusion is a sweeping generalisation straight from the
depths of hell.

The whole problem with finding out what has a -record- lock -is- precisely
because it's bound to a process, not to a file descriptor.  Which means you
must go through every last process on the system (or on all systems in the
case of networked clients) and look at the locks they hold - if that's even
possible, as opposed to just looking at the file.

Also, pretty sure this breakdown of fcntl() describes exactly why filePro
will fail to have a record locked after -one- file descriptor to an open
file is closed, even if others are open; it's apparently never been
filePro's fault, but rather POSIX fcntl() file locking's fault, since
there's zero notification to other lock-holders.  I've always thought
that was filePro's fault for not tracking enough of its own locking.  But
assuming I'm right about it using fcntl(), it appears to be entirely
unavoidable.  My long-overdue apologies to Ken, if my new conclusion is
correct.

mark->

On Mon, Jan 05, 2015 at 11:28:38AM -0500, Nancy Palmquist thus spoke:
> Richard,
> 
> I have had issues with Record Locks on Windows Computers that are
> System Errors and like you said, no sessions are open and no file
> locks are listed in the system logs.  The Windows System has a
> portion of the file locked and has forgotten why and who locked it.
> I don't think filepro can deal with this kind of lock properly or is
> left with no knowledge of the lock existing.
> 
> This is some kind of Windows issue and I have found it is fastest to
> just reboot the server.  I have never found any Administration tool
> that will release the lock.  Even getting all users out by logging
> out and closing sessions does not work.
> 
> I have seen this on Win XP, Win7 and Windows Server versions.  Not
> often, but often enough to be something I check for when the filepro
> locking has been released and users have been reviewed in Computer
> Management on Windows Administration.
> 
> I assume that some broken session has left Windows with a file lock
> and no way to unlock it properly.
> 
> Nancy
> 
> 
> On 12/19/2014 3:10 PM, Richard Kreiss wrote:
> >One of my clients called today with a locked record problem.
> >
> >Short of rebooting his Windows 8 server, is there way to clear the lock on this record?
> >
> >1. Record is locked with no one logged into the system
> >2. Reports hang-up on this record
> >3. The only possible time to reboot the server would be just after midnight.
> >
> >Is there a way that, when using either Procexp or procmon to see what might be locking this record if rclerk or rreport are running on a local computer and not the server?
> >
> >
> >Richard Kreiss
> >GCC Consulting
> >
> >Office: 410-653-2813
> >
> >
> >_______________________________________________
> >Filepro-list mailing list
> >Filepro-list at lists.celestial.com
> >Subscribe/Unsubscribe/Subscription Changes
> >http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> 
> -- 
> Nancy Palmquist         MOS & filePro Training Available
> Virtual Software Systems    Web Based Training and Consulting
> PHONE: (412) 835-9417           Web site:  http://www.vss3.com
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 

-- 
Audio panton, cogito singularis.