1

Topic: How program to disconnect the user in FB 1.5.3?

There is the list of users received through Security Service. It is required to disconnect arbitrarily taken user from a DB on the server. I.e. the program in which it works should lose a connection to basis. It probably to make through Api? Or generally somehow?
At present for switch-off the program launches stored procedure which does POST_EVENT a type "DISCONNECT _ <NAME>". At start after login each program  at itself corresponding . And receiving such  under abnormal condition it is extinguished. It would be desirable to leave from it.

2

Re: How program to disconnect the user in FB 1.5.3?

x77> it would be desirable to leave from it.
From event-a? Put down a flag and let all clients check it also fall off.

3

Re: How program to disconnect the user in FB 1.5.3?

It is a pity that it is impossible.
Yes at a flag the pluses/minuses, as well as at ...  asynchronously works, at least. That the same to achieve a flag, it is necessary to carry out its check in process. If the regular decision is not present - that let and lives, I simply wanted to be convinced that it really is not present.

4

Re: How program to disconnect the user in FB 1.5.3?

x77> that the same to achieve a flag, it is necessary to carry out its check in process.
"In a flow" you wanted to tell? It is possible to check in the timer.
By the way,  does not guarantee "" clients on the new.

5

Re: How program to disconnect the user in FB 1.5.3?

Yes, in a flow.
With repeated connection here separate . The previous developer lifted server MSSql, in it is mega - the table in which there is mega a flag. At start of the program it at first to break on MSSql, checks this flag and if it is exposed - that to be connected to FB does not try at all. From so.

6

Re: How program to disconnect the user in FB 1.5.3?

And how by means of ROLES to forbid the disconnected client to be connected again?

7

Re: How program to disconnect the user in FB 1.5.3?

Thanks for idea. I will think.

8

Re: How program to disconnect the user in FB 1.5.3?

wrote:

  the rights to a role.

The dynamic rights? You on what push young children? And from
It does not rescue connection. Simply the role will automatically be dropped in NONE.

9

Re: How program to disconnect the user in FB 1.5.3?

>  the rights to a role.
Yes well, . It not the decision.
Though the variant with  is even worse.
P.S. , since 2.1, the task has
The effective and unambiguous decision.

10

Re: How program to disconnect the user in FB 1.5.3?

Actually, "the unambiguous and effective decision" for all it is it to write normal "".
All these dances with a tambourine are necessary at present only that it was possible to chop off all users, to replace  or to make  /  bases. But to write  while will be nobody.
The wild thought wanders to make something of type of the mini-app-server which will be twisted on the server  and on a certain signal it is stupid to stop service . And on other signal it is stupid to include.
Tried to do on simple,  basis. At option Forced - clients fall off, but can repeatedly come. At option Deny attachments - while clients hang,  it is impossible to make. If clients do not hang -  transits, but all the same they then are repeatedly connected. I do not catch up with something with it ... The DBMS version - 1.5.3.
, and what unambiguous decision in 2.1?

11

Re: How program to disconnect the user in FB 1.5.3?

All the same it will be necessary to give the message: "the DB is inaccessible on N hours", i.e. or to add clients or to pass to a normal DB or a complex of programs of type Net Message
______________________________________________
You have the right to keep silence! All that you tell can be used against you in court!

12

Re: How program to disconnect the user in FB 1.5.3?

Messages from the program are just optional. Delivered the letter on the general group "in basis not to climb with 10 to 12", and all. If who does not read mail - its problems. And the program at a breakaway of communication or inaccessibility of basis produces the regular message: "there is no communication with the server".

13

Re: How program to disconnect the user in FB 1.5.3?

x77 wrote:

messages from the program are just optional. Delivered the letter on the general group "in basis not to climb with 10 to 12", and all. If who does not read mail - its problems. And the program at a breakaway of communication or inaccessibility of basis produces the regular message: "there is no communication with the server".

wrote:

  basis. At option Forced - clients fall off, but can repeatedly come

Notified, then  all and work. Who did not hide I is not guilty. If comes, it prevents that-l?

14

Re: How program to disconnect the user in FB 1.5.3?

x77 Writes:
x> the wild thought wanders to make something of mini-app-server type;
x> which it will be twisted on the server  and on the defined
x> it is stupid to signal to stop service . And on another
x> it is stupid to signal to include.
The service should not be stopped, it is fraught with side.
Write the unpretentious port-mapping, all connections with the server through it start up. On a certain signal this port-mapper tears all connections.

15

Re: How program to disconnect the user in FB 1.5.3?

[quote =] about the RIGHTS generally no concept has.

Almost so it also is. The connection always goes under . Users in basis are got, and even any rights are registered by it, but is real - the card of the rights is assigned and traced program.
But I yet do not sweep aside your variant. It is possible to get the system user under whom there will be the first connection receiving the list of users from the server. To assign to it necessary for this right not directly, and through separately got role. Here then this role can though be killed though anew to create - not a problem. A question in other: whether "the user deprived of civil rights" with the disconnected role physically  to basis can? If can - that it gives nothing.
[quote =] notified, then  all and work. Who did not hide I is not guilty. If comes, it prevents that-l?

Yes, prevents. At us regular preventive maintenance becomes as follows. After the notification, users are disconnected, the service stops, the basis is renamed. The service is launched, becomes  /  the renamed basis. The basis is renamed reversely. Users are notified on possibility to continue operation.
And so, as the Microsecond validly noted, it would not be desirable to disconnect service. And if after switch-off any woodpecker again gets into basis - you cannot simply rename it. And to do  /  bases to which users are connected are at least, loss of the data.