From owner-freebsd-questions Thu Jul 4 15:39:10 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA10139 for questions-outgoing; Thu, 4 Jul 1996 15:39:10 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA10129; Thu, 4 Jul 1996 15:39:08 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199607042239.PAA10129@freefall.freebsd.org> Subject: Re: Majordomo problem (help) To: dbabler@Rigel.orionsys.com (Dave Babler) Date: Thu, 4 Jul 1996 15:39:08 -0700 (PDT) Cc: dwhite@resnet.uoregon.edu, bala@cst.com.au, freebsd-questions@freebsd.org In-Reply-To: from "Dave Babler" at Jul 4, 96 11:01:07 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dave Babler wrote: > > > > I spent most of yesterday afternoon trying to get Majordomo to work and > have exactly the same error. The error 137 (according to the Majordomo > docs) is probably being returned from the mailer (sendmail in my case) > but the man page for sendmail points to the syscodes header file which > does not contain 137. If you run 'top' while majordomo runs, you'll see that > it starts out with a few hundred k of swap, then every few seconds it > grabs more and more and more and eventually runs out, faults and is > killed. I assume it's a permissions error, but all I have to go on is the > error code (136 or 137). If you find out anything more, please let me know. majordomo is very picky about permissions on files and directories in general, make things owned by a majordom user with group write permission enabled. jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB