Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   Contact Center Applications (http://support.avaya.com/forums/forumdisplay.php?f=3)
-   -   Forcing All CMS Supervisors Closed (http://support.avaya.com/forums/showthread.php?t=6408)

marzahn 05-06-2015 11:15 AM

Forcing All CMS Supervisors Closed
 
First off I realize that I am asking for a technology solution to a staff training issue. However I am at my wits end on this one. I have a large number of call center supervisors who leave their CMS client running for days at a time.
  • This requires me to run the kill command on them when doing full backups and other cmsadm proceedures.
  • It also means that they corrupt their personal CMS cashe from time to time.
I have attempted to modify the behavior of call center manager managers with calls and e-mails. But so far this has not been enough. This an 8 to 5 operation. So staff should be out of the system over night.

Is there a command that I can run from a script that will run the "kill -9" command on everyone on a nightly basis? The only thing I have thought of is too "kill" everyone and issue a shutdown/reboot command from a terminal Emulator session every night before I go to bed. Any ideas out there?

shaikht 05-07-2015 12:07 AM

Hi Bill,

We have APS solution which will disconnect supervisor session after specific duration.
It will also not allow same id to create new session if one is already running.

Please engage your Account manager so that they can engage APS team for same. Please be notified that APS team works on project basis and will be billable.

On command, you need to create a script which will search for win_io_man process.Supervsior sessions will have win_io_man process associated with it. So once script will be searching all active process and will be killing them.

I hope it helps.

marzahn 05-08-2015 07:05 AM

That is Useful
 
I appreciate that Shaikht. However I would like to learn to do this work myself. I have looked through the help files and it looks as though all the scripts do pretty "plain vanilla stuff" such as reports.

I guess I'm just one of those never satisfied guys.:) It should not be too hard to set up. I'm going into good practice related to the kill command on the Solaris OS.

sumit007 05-20-2015 12:01 AM

Forcing All CMS Supervisors Closed
 
Hi Bill,
You can involve APS for this for neat and clean work.
But if you dont want then you can follow below procedure.
1. Make a script in which you can have find "win_io_man" and "chip" process
2. Kill them all
3. Make a cronjob entry for this script. before backup schedule means to say that if backup runs at 2:00 everyday in morning then you need to make this script to run at 1:30 everyday.
4. This will kill all Supervisors

Please make a note here that i always recommend to involve APS to get this kind of custom solution to prevent unnecessary problems.

if you are following above steps you must know that what you are doing.

yadav29 05-21-2015 12:25 PM

You can set a cronjob script for that like you have a office 8*5 so you can schedule in the mid of the night.
in the cronjob script you have to do the scrptig where you will find any session of CMS supervisor it can kill automatically.
yo can check via this command:-
ps -ef |pid (CMS supervisor)

marzahn 05-27-2015 08:42 AM

Good One
 
Quote:

Originally Posted by yadav29 (Post 17371)
You can set a cronjob script for that like you have a office 8*5 so you can schedule in the mid of the night.
in the cronjob script you have to do the scrptig where you will find any session of CMS supervisor it can kill automatically.
yo can check via this command:-
ps -ef |pid (CMS supervisor)

I appreciate that. I did some research and it looks pretty straightforward.


All times are GMT -7. The time now is 06:51 PM.