From owner-freebsd-hackers Mon Jun 10 10:30:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26768 for hackers-outgoing; Mon, 10 Jun 1996 10:30:15 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA26763 for ; Mon, 10 Jun 1996 10:30:12 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA09243; Mon, 10 Jun 1996 11:29:56 -0600 Date: Mon, 10 Jun 1996 11:29:56 -0600 From: Nate Williams Message-Id: <199606101729.LAA09243@rocky.sri.MT.net> To: reichert@internet.com Cc: hackers@FreeBSD.org Subject: Re: Ahhhhhhhhhh! In-Reply-To: <199606101718.NAA27079@oneida.internet.com> References: <199606101718.NAA27079@oneida.internet.com> Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Brian Reichert writes: > Long ago, I took to using procmail to break out my mail upon delivery to > various folders. I noted that several times _daily_ that procmail was > dropping core. > > Well, I hacked procmail to requeue the mail upon a segfault, and after a few > days, guess what I found? > > Seventy-nine mail messages from hackers, bugs, and stable ! > > I haven't gone pawing through debuggers to see what the issue is, but will > have to if I want my mail to be delivered. > > Have anyone else seen wierd behaviour from this? I note that even with with > all of the debugging stuff turned on, the resulting core file died way out > in a library somewhere... Hmm, never. Maybe I've been lucky, but I've never had *any* problems with procmail that weren't operator error (like moving the binary and not updating my .forward, creating bogus .procmailrc files). > For what it's worth, I'm running 2.1R and procmail v3.10. I was running 3.10 for quite a while, but upgraded to a newer version earlier this year. procmail v3.11pre3 However, I know that many other people who use procmail also have had problems. I guess I'm just lucky! Nate