ANK@CUNYVMS1.BITNET (08/05/87)
>We run KERMIT in two modes on our VAX. (There are names -- local and >remote -- for the modes but I can never remember which is which.) >Anyway, one mode is where you log in to the VAX from a PC and then run >KERMIT, typically in server mode. This works fine. But when a local >(dumb terminal, say) VAX user uses KERMIT to connect to a modem line >and dial out from the VAX, it brings the system to its knees. NOT true unless the user does not alloc the device: I have found the alloc faster that selecting the line within Kermit $ ALLOC TTYXXX: Kermit32> set line TTYXXX: before dialing out gives a faster response for me, why I do not know ...maybe someone else would know the answer >MONITOR PROCESS/TOPCPU shows nothing unusual. But users only get at >best 50% of wall clock time; it seems like something is eating the >system at some interrupt level. What are the other Process stats because the TOPCPU is not the only thing that gives you the cause of system slow-down I would be interested in the other responses that you get, since this could be crucial in determining if SET HOST/DTE is a better solution that using FOR* SOFTW* to connect to other VAX's Anil Khullar {Ph.D. Prog in Psychology C.U.N.Y. Grad. Center. 33 W 42 St. Box 295, New York NY 10036 } BITNET:ank@cunyvms1 INTERNET:ank%cunyvms1.BITNET@wiscvm.edu ========================================================================== ON THE SEVENTH DAY GOD RESTED AND WATCHED CELTICS PLAY AT THE GARDEN ========================================================================== [DISCLAIMER: They say after Boston there is heaven, I agree; I say after LispM there is nirvana, they don't. This and other such opinion are held dearly by me, my employers and the institution I represent do not necessarily hold that view. I am sole culprit of such fantasies. No living being is responsible, however unsolicited support is welcome]