From owner-freebsd-stable Thu Sep 14 15: 7:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [204.117.82.9]) by hub.freebsd.org (Postfix) with ESMTP id 55D7E37B42C for ; Thu, 14 Sep 2000 15:07:35 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by yertle.kciLink.com (Postfix) with ESMTP id 62B622E444 for ; Thu, 14 Sep 2000 18:07:34 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.0/8.11.0) id e8EM7YZ85724; Thu, 14 Sep 2000 18:07:34 -0400 (EDT) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14785.19494.256991.220906@onceler.kciLink.com> Date: Thu, 14 Sep 2000 18:07:34 -0400 (EDT) To: FreeBSD-Stable Subject: Re: negative proccnt In-Reply-To: References: <14785.15822.898420.198946@onceler.kciLink.com> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "CB" == Chris BeHanna writes: CB> You might consider switching to majordomo or listproc. Both are CB> written in perl, and will run natively under FreeBSD. Have you ever tried to manage a multi-thousand member list with those? With lyris, I have to do zero administration work to clean up after the list manager. With every other list manager, I had to do lots of work manually to clean out bogus addresses and such. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message