![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Session control and management Topic Summary: Daemon or script for clean shutdown of inactive client sessions Created On: 14-Mar-2007 08:37 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello:
I'm a DOORS admin, manager and all of many databases and projects inside them.
This is a big department with many people working on the server.
Some of them working from more or less separated physical offices.
And many of them drag on the same problem year after year: the analysts and other kind of workers (developers that work with TAU over DOORS and all) DON'T SHUTDOWN their computers after the working day or when they have to be several hours outside the work station.
This is more corageus when the DON'T EVEN CLOSE THE CLIENT SESSION.
Has anyone work in any kind of solution of developing and having a daemon in the server side looking for inactive sessions in order to shutdown them properly and closing or at least freezing the client session?
I'm noticing that some people has sessions opened since weeks...
The best and kindest way is to make a corporative warning about the problems this could generate and create some kind of working guides and conventions. But I'm afraid and I have the experience that this does not work with people...
The problem is that I make back-ups all nights, but day after day the number of locked modules and opened porcesses increases and I've to sometimes make a controlled shutdown and be chasing the people...
So, what I'm asking for is about if anyone has practiced in this kind of scripts or daemons because I'm thinking on developing one for us.
I would like at least to make an open discussion about this issues.
Many thanks in advance.
Best regards.
|
|
![]() |
|
![]() |
|
Don't know about a Flex resolution.
You can eliviate some of the issues by insisting all clients use READ_ONLY as the default open mode, both when they double click on a module and when they follow a link indicator. If so, folks will have lots of modules open for R but won't be locking anyone out for hours. The configure utility will let folks do that to their clients. Its tough to enforce since its contolled at the client level. DefOpenMode READ_ONLY DefOpenLinkMode READ_ONLY Backups usually prefer nobody is in the database. Your auto-backup utility that runs at 1am could realistically shut down the DOORS service, do backups, and restart the service. Tough luck to anyone logged in at 1am. If its interests you, you CAN get a list of folks still logged in (with their Client names) by running the DBADMIN.exe script from a DOS *.bat file. It would look something like attached. You could then write some VB script to read the report and do something nasty to the users or the clients. - Louie |
|
![]() |
|
![]() |
|
Thank you very much Louie
Very interesting advices. Bets regards. |
|
![]() |
|
![]() |
|
If users access DOORS via Citrix, you can define properties for the user sessions such as:
- End a disconnected session: x - Active session limit: x - Idle session limit: x etc., where x can be specified in minutes, hours or days. Ken McNair. |
|
![]() |
Telelogic DOORS
» Administration
»
Session control and management
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.