From owner-freebsd-isp Sun Feb 22 03:07:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16874 for freebsd-isp-outgoing; Sun, 22 Feb 1998 03:07:22 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mailgw00.execpc.com (sendmail@mailgw00.execpc.com [169.207.16.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16834 for ; Sun, 22 Feb 1998 03:07:16 -0800 (PST) (envelope-from jeff@mountin.net) Received: from hilltop (geordi-laforge.isdn.mke.execpc.com [169.207.65.48]) by mailgw00.execpc.com (8.8.8) id FAA19781 for ; Sun, 22 Feb 1998 05:07:14 -0600 (CST) Message-Id: <3.0.3.32.19980222050452.00729710@rustbelt.com> X-Sender: jeffm@rustbelt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 22 Feb 1998 05:04:52 -0600 To: isp@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: popper slow Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Recently installed the popper port (qpopper 2.41beta1) and find that it hangs or is real slow and sporadic if a moderately large message, say 35K, is in the mailbox. It doesn't matter if the total mail is 20 messages for 100K or if I have almost 1M of mail. Rather odd, since I'm doing nothing fancy with it. The inital parsing is quick. Running 2.2.5 on a P166 w/64MB, several disks, with near nothing for load and connecting via 128 ISDN, but is the same on the network. Tempted to back off to 2.4, but don't feel like hacking the port, yet. On a slower system with an older version I can pull almost any size message without a hitch. I've also noticed that it doesn't clean the lock files. Or is that a feature? At least it doesn't prevent a new connection. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message