kelso@gwusun.gwu.edu (John Kelso) (09/13/89)
I've been beating my haed against a problem for the last few days, and
I'm hoping someone out there might be able to point out what I'm doing
wrong.
Here at GWU all of our modems are connected to an HP 835-SE, which is
our main general-purpose computer.
Some users have accounts on our Vax, and wish to dial-in and use it.
How we've handled this is to create an account called "vax", whose
.profile (it uses ksh) consists of the lines:
/usr/bin/telnet vax
exit
In general this works fine. When the user logs off the Vax, they get
logged off the HP, and all is well. The problem occurs when the modem
connection is broken while the user is logged on. What happens is
that the telnet session on the HP "runs away", with cpu time piling up
almost as fast as real time. (Idle time is also piling up.) These
numbers are reported by the "w" command.
I've tried the following workarounds, none of which seem to make any
difference.
change the .profile to be the single line:
exec /usr/bin/telnet
add a timeout to the shell.
I've noticed that if you kill the shell process, the telnet process
doesn't die.
This happens regardless of what machine you telnet to. Suns, Vaxen, even
IBM's all show the same problem.
The problem doesn't occur if you use rlogin instead of telnet. Alas,
rlogin isn't available on our Vax.
Any comment, workarounds or advice would be very much appreciated.
Thanks,
John
--
John Kelso, System Engineer, George Washington University
SEAS Computing Facility, 725 23rd St NW, Washington DC 20052
kelso@gwusun.gwu.edu -or- uunet!gwusun!kelso
--rdg@hpfcmgw.HP.COM (Rob Gardner) (09/20/89)
> Some users have accounts on our Vax, and wish to dial-in and use it. > How we've handled this is to create an account called "vax", whose > .profile (it uses ksh) consists of the lines: > /usr/bin/telnet vax > exit > > In general this works fine. When the user logs off the Vax, they get > logged off the HP, and all is well. The problem occurs when the modem > connection is broken while the user is logged on. What happens is > that the telnet session on the HP "runs away", with cpu time piling up > almost as fast as real time. (Idle time is also piling up.) These > numbers are reported by the "w" command. No promises, but try the following .profile to workaround the bug: trap "kill -9 0" 0 1 2 3 /usr/bin/telnet vax exit Rob