Q re killing sessions

I mailed an answer to this a few days ago, but am afraid our mail server is doing funny things. Forgive me if this is a duplicate post. We have solved this problem at our company by creating a turnkey login that is restricted to only doing certain things - executing one script or perhaps a series of menu options. If you want a user to be able to run tbmode and only tbmode, create a Unix login ( call it killer, for example ) with the same user number as Informix. But instead of a shell, place the full path of the script you want executed in the passwd file. The script would prompt the user for a process to disconnect, then issue the tbmode -z and exit. The key thing is to not allow the user any other access than to this one script. Hope this helps. Mike Ballentine --------------------------( Forwarded letter 1 follows )--------------------- Date: Thursday, 30 October 1997 8:01am From: barryleb@atl.mindspring.com Subject: Q re killing sessions Date: Thu, 30 Oct 1997 07:11:34 -0600 Reply-To: barryleb@atl.mindspring.com Organization: MindSpring Enterprises, Inc. Sender: informix-list-owner@rmy.emory.edu To: informix-list@rmy.emory.edu X-Informix-List-Id: <news.44670> I am the sole DBA at my company. However, there are times when I am not available and an errant session needs to be killed. The only way I know to kill a session cleanly is with the onmode -z command. Is there any way to give someone the ability to kill an informix session using onmode without giving them the informix password or compromising security elsewhere? Barry Leb National Linen Service 1420 Peachtree Street MS #314 Atlanta, GA 30309 (404) 853-6119 (404) 853-6485 fax e-mail: barryleb@mindspring.com