Telnet Disconnects

Manual Cleanup After TELNET Disconnect

When you use TELNET over the Internet to connect to a network of HP-UX and MPE systems, it is quite common to be disconnected, especially if you are using SLIP or PPP over a modem. If you are used to MPE's fanatical care in cleaning up aborted connections, you will be very surprised when you reconnect to the same system -- your old login may still be active!

Just because you were disconnected from your end of the TELNET circuit does not mean that the system at the other end got the message and logged you off. My experience is that unless you logoff normally, the host system may still show your TELNET login as active. If you do not manually delete these ghost logins, they can hang around until the system is shut down.

When you login again to the UNIX system, use who to see if you are still logged in. If you had previously used vt3k to make a virtual terminal connection to the HP 3000, do so again now. After your MPE :Hello command, do a :Showjob job=@s to see if you are still active. If you see two sessions for yourself, first try using :abortio on the terminal device number, then try :abortjob on the session number. Once :showjob shows your previous session is gone, :exit back to HP-UX.

   >vt3k mickey.robelle.com
   :hello sam.spade
   :showjob job=@s
   :abortio 22
   :abortjob #s1234
   :exit

On the UNIX system, use who to see if your previous login is still present. Then use ps -uusername to list all the processes for your username. For those processes with the same ttyv value as your previous login, do kill -9 nnnn.


   >who
   >ps-usspade
   >kill -9 16138