From owner-freebsd-isp Tue May 30 14:30:27 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.ahnet.net (mail.ahnet.net [207.213.224.25]) by hub.freebsd.org (Postfix) with ESMTP id AEA9C37BC51 for ; Tue, 30 May 2000 14:30:25 -0700 (PDT) (envelope-from sumbry@affinity.net) Received: from sql.ahnet.net (control.ahnet.net [207.213.224.10]) by mail.ahnet.net (Postfix) with ESMTP id E4E295ECA; Tue, 30 May 2000 14:25:10 -0700 (PDT) Date: Tue, 30 May 2000 14:25:11 -0700 (PDT) From: "Sumbry][" X-Sender: sumbry@sql.ahnet.net To: lambert@cswnet.com Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source In-Reply-To: <200005302026.PAA06858@troi.csw.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > We tried Cucipop on our 3.2-STABLE mail server. It worked until we added > a second CPU. At that point Cucipop would work fine for a couple of days > and then just quit. We didn't have time to debug it so we just went back > to QPopper. > > I would be interested in hearing from people with SMP systems and Cucipop. Re my previous message, we also are running cucipop on a Dual P3 processor box, running 3.3. No problems at all. ----- Sumbry][ | Affinity Internet Inc | http://affinity.net | sumbry@affinity.net I'll believe psychics when one phones me, just in the nick of time, yelling, "Duck!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message