Chuck Mattern wrote:
> I've got an annoying problem with a simple solution but a more
> eloquent solution would be better. I have users connecting to my
> systems with telnet clients that will drop the connection leaving
> applications still running. The client pieces are located on about
> 8,000 individual disks which I don't own so fixing that part of the
> puzzle is a tad daunting at the moment. The simple solution is to
> locate the sessions, connect to the DB server and cleanly terminate
> their database connections then kill the processes. A more elegant
> and acceptable solution to my management would be to take over the
> session and terminate it from within. Has anyone here had any
> experience with hijacking an abandoned telnet sessions either from Perl
> or C?

Sorry for the delay in this, the news server I access has been down
for days...

We wrote/sell a program call PEEK. This software let you see what
someone is doing AND lets you type keystrokes on their behalf.
You can control who can look at who, you can use an audit trail to
log what is going on. And you can script it, so you could send the
keystrokes you wish.

But it is not for GUI sessions. It'll work for any telnet/xterm
text window, serial, etc., just not a full GUI app. Is this helpful?
You can get details by sending a message to peek@computron.com or
visit www.computron.com

Thanks!

Randy Styka, randy@computron.com