Subject | Killing remote user via Code |
---|---|
Author | Johannes Pretorius |
Post date | 2004-04-29T05:22:01Z |
Interesting posting I read on the borland - newsgroup
about IB 7 and up, that one can kill a remote user via updating a
temp table that , it seems , logs and monitors all the connections. As
follows :
in IB 7.x
UPDATE TMP$ATTACHMENTS SET TMP$STATE = 'CANCEL'
WHERE (TMP$ATTACHMENT_ID = 12345)
Considering this I was wondering if the need has ever been there for
FireBird users to
do something like this AND does the people who know how, think that this
is a good solution
to move towards environment where one can control user access and stats per
database better as in
MSSQL ??
I just thought I'll ask the question ??
Thanks in advance for any comments
Johannes Pretorius
----------
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.672 / Virus Database: 434 - Release Date: 28/04/2004
[Non-text portions of this message have been removed]
about IB 7 and up, that one can kill a remote user via updating a
temp table that , it seems , logs and monitors all the connections. As
follows :
in IB 7.x
UPDATE TMP$ATTACHMENTS SET TMP$STATE = 'CANCEL'
WHERE (TMP$ATTACHMENT_ID = 12345)
Considering this I was wondering if the need has ever been there for
FireBird users to
do something like this AND does the people who know how, think that this
is a good solution
to move towards environment where one can control user access and stats per
database better as in
MSSQL ??
I just thought I'll ask the question ??
Thanks in advance for any comments
Johannes Pretorius
----------
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.672 / Virus Database: 434 - Release Date: 28/04/2004
[Non-text portions of this message have been removed]