![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Session control and management Topic Summary: Restrictive session control daemon Created On: 14-Mar-2007 08:35 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello:
I'm a SYNERGY 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 developers and other kind of workers (analysts that work with TAU over SYNERGY collaborative environment) 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 (SYNERGY/CM Desktop client, or the different IDE plug-ins).
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 "zombie", not controlled or old ccm procceses 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.
|
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
Session control and management
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.