Re: Restrict Access

[Paul DuBois]

At 11:51 AM -0700 7/27/99, Thimble Smith wrote:
>At 15:29, 19990727, sinisa@stripped wrote:
>>toxalot@stripped writes:
>> > Access to the database requires a piad subscription and we don't want
>> > companies buying one subscription and then letting all employess use the
>> > same user name.
>>
>>select get_lock("user_name",10000);
>>.........
>>
>>select release_lock("user_name");
>
>Since the lock names are global (i.e., not qualified by the database
>or user or anything else), I would suggest using a longer name for
>your locks, which includes a unique identifier for YOU, one for the
>COMPANY you're dealing with, and finally the specific USER you are
>locking out.  For example, you might use
>
>    select get_lock("YOUR-DB-NAME;The Company;user_name", 10000);
>
>You don't know who else is using locks on the database system that
>you're running.
>
>Huh, that makes me wonder - what privileges are required to select
>get_lock()?  Would it be possible, on a shared system (like at an
>ISP that provides MySQL support), for someone to deny service to a
>totally unrelated account by acquiring locks that they depend on,
>and not releasing them?


I have a fairly basic question about GET_LOCK():  what is it that's
being locked?

-- 
Paul DuBois, paul@stripped