Discussion Locked

Preventing the use of the Close Button i

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
This is a similar question to another one posted here, but I was wondering if anyone had a suggestion for preventing the use of the x button in a Windows 98 application. We have several hundred users running a telnet application to connect to a Unix server. Most of them click the x button in the title bar to exit, leading to hung resources in the system. Anyone know of a quick registry setting or some other type of solution?? Thanks.

15 replies

by trmcdougle

I do not think that is practicable as there are too many ways to close a windows program (and ways to kill windows, which would have the same effect).

You might try a different telnet program (we use TeraTerm Pro which is free), but I do not expect that the problem is at the client end. You can even get the source code of this so could attempt to make a custom client (but check the usage terms first). The homepage is:-
http://hp.vector.co.jp/authors/VA002416/teraterm.html

However what Ithink you should try to get the host side fixed to deal with a lost connection more gracefully. It should be technically possible, after all our VMS system manages it when our telnet sessions are closed that way!

by jpereira

The problem is not at the client end. When your click the close button on the terminal, it sends a hang up signal to the shell that's running on the terminal. If I do the same thing using telnet on my PC, the shell at the other end disappears as do any child processes (unless they have been "nohupped").

You don't say what resources are left hung. If it is an application, I suspect that it is catching the hang up signal and then ignoring it. If it's background processes, they are probablybeing run nohupped, which I believe some shells do by default.

by disillusionedmember

Educate users on how to gracefully terminate the UNIX/Telnet session without using the close box. The close box should not be used until the session terminates. Try "Blast" or "VersaTerm" telnet programs.

by mjohnson

Note to other responders:
I know both Tandem and IBM OS/400 do NOT like being disconnected from a Telnet session ungracfully. It creates an "orphan" process on the server. The server does not know the session was closed on the client side. This is a design flaw on the client side. The X box just exits the program. It does not close all of its processes first.

As the others have suggested, try another Telnet emulator. I'm afraid I cannot give you a suggestion. Even IBM Client Accessmakes orphans. The giggalo!! LOL

by eyek

Try to use either Exceed or PCXware softwares on connecting into a UNIX workstation. This will prevent your users accidentally disconnect their sessions. Our Engineers are using this utility without any problem and they love it. I recommend you
to check it out.

by ab3_tek

I too highly recommend Exceed as your software to connect to a Unix box. The software has build in functionality that allows connections and disconnections to happen the 'right' way and minimize orphan processes.

This discussion is closed to new replies.