From owner-freebsd-questions  Mon Mar 18 07:16:14 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA26386
          for questions-outgoing; Mon, 18 Mar 1996 07:16:14 -0800 (PST)
Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA26381
          for <questions@freebsd.org>; Mon, 18 Mar 1996 07:16:11 -0800 (PST)
Received: by freebsd.netcom.com (8.6.12/SMI-4.1)
	id JAA12308; Mon, 18 Mar 1996 09:20:16 -0600
From: bugs@freebsd.netcom.com (Mark Hittinger)
Message-Id: <199603181520.JAA12308@freebsd.netcom.com>
Subject: re: Freebsd and Majordomo out of memory
To: questions@freebsd.org
Date: Mon, 18 Mar 1996 09:20:16 -0600 (CST)
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> From: Rob Cima <rcima@global-image.com>
> I'm running FreeBSD 2.0.5, majordomo 1.93 and perl 5.001m. I get out of
> memory errors whenever a message gets sent to majordomo, and the majordomo
> process just sits until it is killed.

It might be because majordomo creates a bunch of sendmail processes to 
deliver the message.  If you had a large mailing list you might see this
behavior.

I modified the sendmail switches used in the /etc/aliases entry for each of
the mailing lists that I ran.  I included the '-odq' switch for sendmail.

This switch is your friend.

Each sendmail process will queue its mail to be sent later and exit.  You can
then have your tradition -q1h process come along and send mail in a serial
fashion rather than a parallel fashion.  (I used -q30m to speed things up
a little).

Sendmail consumes a lot of resources, and if you have too many simultaneous
sendmails bad things will happen.

Later!

Mark Hittinger
Netcom/Dallas
bugs@freebsd.netcom.com