Identify user in update mode

[Jay Ashworth]

----- 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.

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.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274