Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 10 Nov 2000 15:42:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 10 Nov 2000 15:42:46 -0500 Received: from chaos.analogic.com ([204.178.40.224]:21120 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id ; Fri, 10 Nov 2000 15:42:25 -0500 Date: Fri, 10 Nov 2000 15:42:12 -0500 (EST) From: "Richard B. Johnson" Reply-To: root@chaos.analogic.com To: Andrea Arcangeli cc: "Jeff V. Merkey" , linux-kernel@vger.kernel.org Subject: Re: [Fwd: sendmail fails to deliver mail with attachments in /var/spool/mqueue] In-Reply-To: <20001110212156.A4568@inspiron.suse.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 10 Nov 2000, Andrea Arcangeli wrote: > On Fri, Nov 10, 2000 at 03:07:46PM -0500, Richard B. Johnson wrote: > > It isn't a TCP/IP stack problem. It may be a memory problem. Every time > > sendmail spawns a child to send the file data, it crashes. That's > > why the file never gets sent! > > Sure that could be the case. You should be able to verify the kernel kills the > task with `dmesg`. > > However Jeff said the problem happens over 400K and a 500K attachment shouldn't > really run any machine out of memory, so maybe this wasn't his same problem? > > Andrea > It ran out of memory. The file got sent fine after I got rid of all the memory-consumers. Looks like a sendmail bug where they expect to load a whole file into memory all at once before sending it. I always thought you could read from a file, then write to a socket. Maybe I'm old fashioned. Cheers, Dick Johnson Penguin : Linux version 2.4.0 on an i686 machine (799.54 BogoMips). "Memory is like gasoline. You use it up when you are running. Of course you get it all back when you reboot..."; Actual explanation obtained from the Micro$oft help desk. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/