Subject | Re: [firebird-support] 2 copies of fb_lock_mgr |
---|---|
Author | Milan Babuskov |
Post date | 2008-08-08T13:14:21Z |
Nick Upson wrote:
When you access Classic via xinetd or inted, it always spawns a single
fb_lock_mgr since system username is 'hardcoded' in (x)inetd config file.
So, if I run:
$ bin/isql localhost:/path/whetever.fdb -user fbuser -pass ****
or as root:
# bin/isql localhost:/path/whetever.fdb -user fbuser -pass ****
I will end up with a single fb_lock_mgr.
However, if you try to access the database file directly (i.e. no
hostname in the path):
$ bin/isql /path/whetever.fdb
Another fb_lock_mgr might get spawned (depends on the account you are
using). This second form of attaching to database can work without
Firebird username and password if you have enough privileges on the
database file itself as a user.
HTH
--
Milan Babuskov
http://www.flamerobin.org
http://www.guacosoft.com
>> Accessing via different user accounts ('user' as in Linux user). Run aOk, let's go through this from the start.
>> command like 'ps aux | grep fb_lock_mgr' to see the accounts fb_lock_mgr
>> is running under.
>>
> I've just tried this, I had some connections from a non-root user already,
> then ran isql as root - still only 1 fb_lock_mgr running
When you access Classic via xinetd or inted, it always spawns a single
fb_lock_mgr since system username is 'hardcoded' in (x)inetd config file.
So, if I run:
$ bin/isql localhost:/path/whetever.fdb -user fbuser -pass ****
or as root:
# bin/isql localhost:/path/whetever.fdb -user fbuser -pass ****
I will end up with a single fb_lock_mgr.
However, if you try to access the database file directly (i.e. no
hostname in the path):
$ bin/isql /path/whetever.fdb
Another fb_lock_mgr might get spawned (depends on the account you are
using). This second form of attaching to database can work without
Firebird username and password if you have enough privileges on the
database file itself as a user.
HTH
--
Milan Babuskov
http://www.flamerobin.org
http://www.guacosoft.com