🚀 go-pugleaf

Return-Path: <xerox@pharmvax1.ab.umd.edu>
Received: from pharmvax1.ab.umd.edu by sumex-aim.stanford.edu (4.0/inc-1.0)
	id AB15174; Wed, 18 Jul 90 06:38:14 PDT
Message-Id: <9007181338.AB15174@sumex-aim.stanford.edu>
Date: 18 Jul 90 09:29:00 EDT
From: xerox@pharmvax1.ab.umd.edu
To: "skarupa" <skarupa@sumex-aim.stanford.edu>

From:	PHVAX1::WINS%"<skarupa@sumex-aim.stanford.edu>" 18-JUL-1990 09:26:34.24
To:	XEROX
CC:	
Subj:	FTP etherpacket deallocation

Return-Path: <skarupa@sumex-aim.stanford.edu>
Received: from sumex-aim.stanford.edu by pharmvax1.ab.umd.edu with SMTP ;
          Wed, 18 Jul 90 09:26:24 EDT
Received: by sumex-aim.stanford.edu (4.0/inc-1.0)
	id AA15059; Wed, 18 Jul 90 06:27:00 PDT
Date: Wed, 18 Jul 1990 6:26:59 PDT
From: Steve Skarupa <skarupa@sumex-aim.stanford.edu>
To: info-100@sumex-aim.stanford.edu
Cc: skarupa@sumex-aim.stanford.edu
Subject: FTP etherpacket deallocation
Message-Id: <CMM.0.88.648307619.skarupa@sumex-aim.stanford.edu>

Problem: with Medley TCP/IP such that after every FTP request, the
(VMEMSIZE 'LISP) increases by 7 pages.  Thus, the vmem eventually fills
up.  By looking at the (STORAGE) results my guess is that some
Etherpackets are getting de-allocated.  Is this a known FTP bug?
Merci.

Stephen Skarupa
skarupa@sumex-aim.stanford.edu