From owner-freebsd-questions Wed Aug 30 22:02:27 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id WAA21864 for questions-outgoing; Wed, 30 Aug 1995 22:02:27 -0700 Received: from paxs.com (gw.paxs.com [204.188.110.1]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id WAA21857 for ; Wed, 30 Aug 1995 22:02:25 -0700 Received: (from thor@localhost) by paxs.com (8.6.9/1.0000000001) id VAA04630; Wed, 30 Aug 1995 21:59:28 GMT Date: Wed, 30 Aug 1995 21:59:26 +0000 () From: Thor Clark X-Sender: thor@localhost To: Network Coordinator cc: questions@FreeBSD.ORG Subject: Re: Installing Majordomo In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@FreeBSD.ORG Precedence: bulk On Tue, 29 Aug 1995, Network Coordinator wrote: > ...this should be simple, but alas... > > Have been trying to install majordomo. Got it to the point where it runs, > but when it runs, it spawns a majordomo or two that use 100% of CPU and > Memory [including swap] Then return with errors like 136 or 139; memory > failure. > > Any idea where I have goofed? > > Thanks, > > Collette > Had this same problem, checked my permissions and aliases several times to no avail. Turned out we were running perl 5.001 (no patches) and Majordomo doesn't like that. Upgraded to 5.001m and had no more problems (at least like these :> Hope this works (this was on Solaris2.4, but that *shouldn't* matter) Thor Clark