Identify user in update mode

[Kenneth Brody]

On 8/2/2011 1:15 PM, Jay Ashworth wrote:
> ----- Original Message -----
>> From: "Kenneth Brody"<kenbrody at spamcop.net>
>
>>> sigh and of course if we collectively bought and opened the code we
>>> could just export this info directly and with no need to guess or deduce
>>> or inefficiently backtrack using external tools, to shm, and/or provide
>>> a nice libfilepro.so that supplies an easy function...
>>
>> So, you are suggesting that filePro create a "who has what locked" database,
>> which is to be updated on every record lock and unlock call that filePro
>> issues, just in case, on some occasions, you want to find out this
>> information?
>
> No, I'm pretty sure what he's actually suggesting is that if we knew the
> internals enough better, then we could *ask the kernel* for the information
> in question, and we'd know how to format it appropriately to get what people
> want.

Well, you can already "ask the kernel" for the PID of the lock's owner, 
which is exactly what showlock does.  How would "knowing the internals (of 
filePro, I assume)" help determine the "who" part?

And, my reading of "just export this info directly" is "have filePro update 
some information, somewhere, every time a record is locked or unlocked". 
However, only the OP could clarify what he meant by that.

> Not that, in fact, *having* a centralized place to get that info would be
> all that hard for the filepro programs to implement; shared memory isn't
> *that* complicated to work with.

filePro already uses shared memory for some functionality on some platforms.

-- 
Kenneth Brody