Date: Thu, 4 Jul 1996 22:30:45 GMT From: James Raynard <fqueries@jraynard.demon.co.uk> To: dbabler@rigel.orionsys.com Cc: dwhite@resnet.uoregon.edu, bala@cst.com.au, freebsd-questions@freebsd.org Subject: Re: Majordomo problem (help) Message-ID: <199607042230.WAA02979@jraynard.demon.co.uk> In-Reply-To: <Pine.BSF.3.91.960704105537.4461A-100000@Rigel.orionsys.com> (message from Dave Babler on Thu, 4 Jul 1996 11:01:07 -0700 (PDT))
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> Dave Babler <dbabler@Rigel.orionsys.com> writes: [re Majordomo causing all the swap to be used up] > 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 Sendmail has a rather strange way of returning codes - apparently these are documented in -current. If I remember rightly, it adds 128 to the error number, so the true error number is 9 (128 + 9 = 137), which corresponds to EBADF (Bad file descriptor). This doesn't seem to get us any further. > 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. Something is clearly causing Perl to go into an endless loop and eat up all the system's virtual memory. Since 99% of Majordomo problems are permissions-related (allegedly), that's what I'd look at first. -- James Raynard, Edinburgh, Scotland james@jraynard.demon.co.uk http://www.freebsd.org/~jraynard/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607042230.WAA02979>