Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!husc6!think!maynard!campbell
From: campbell@maynard.BSW.COM (Larry Campbell)
Newsgroups: comp.os.vms
Subject: KERMIT brings system to its knees
Message-ID: <971@maynard.BSW.COM>
Date: Mon, 3-Aug-87 08:27:23 EDT
Article-I.D.: maynard.971
Posted: Mon Aug  3 08:27:23 1987
Date-Received: Tue, 4-Aug-87 02:00:32 EDT
Reply-To: campbell@maynard.BSW.COM (Larry Campbell)
Organization: The Boston Software Works, Inc.
Lines: 18

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.

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.

We're on a 750 running VMS 4.1 (I know, I know), with KERMIT 3.1.066.

Has anyone else observed this behavior?  Is it a VMS bug or a KERMIT bug?
-- 
Larry Campbell                                The Boston Software Works, Inc.
Internet: campbell@BSW.COM                  120 Fulton Street, Boston MA 02109
uucp: {husc6,mirror,think}!maynard!campbell         +1 617 367 6846