From owner-freebsd-questions  Tue Aug 29 16:19:48 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id QAA28390
          for questions-outgoing; Tue, 29 Aug 1995 16:19:48 -0700
Received: from ns1.win.net (ns1.win.net [204.215.209.3])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id QAA28383
          for <questions@freebsd.org>; Tue, 29 Aug 1995 16:19:41 -0700
Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id TAA10112 for questions@freebsd.org; Tue, 29 Aug 1995 19:24:56 -0400
From: Mark Hittinger <bugs@ns1.win.net>
Message-Id: <199508292324.TAA10112@ns1.win.net>
Subject: re: Installing Majordomo
To: questions@freebsd.org
Date: Tue, 29 Aug 1995 19:24:55 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 973       
Sender: questions-owner@freebsd.org
Precedence: bulk

> From: Network Coordinator <nc@ai.net>
> 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.

When I first tried majordomo I had a very similar effect.  I traced it down
to the attempt by majordomo to execute real-time deliveries of the mail.
Several sendmail processes were getting created simultaneously.

I modified the alias that executes the resend to use an additional sendmail
flag (-odq).  This queues the mail for later delivery.  If you have a lot
of activity on your list then you probably need to do this.  This is 
especially important if you have a lot of subscribers that are on slow
link hosts.

Example line:

test-list: "|/usr/local/majordomo-1.92/wrapper resend -l test-list -r test-list -m -odq -h domain.com test-list-outgoing"

Regards,

Mark Hittinger
bugs@win.net