From owner-freebsd-stable Mon Jul 8 13:17:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E919F37B400; Mon, 8 Jul 2002 13:17:24 -0700 (PDT) Received: from smurf.jnielsen.net (12-254-136-47.client.attbi.com [12.254.136.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5242C43E4A; Mon, 8 Jul 2002 13:17:24 -0700 (PDT) (envelope-from stable@jnielsen.net) Received: from max (max.local [192.168.0.9]) by smurf.jnielsen.net (8.12.3/8.12.3) with SMTP id g68KHFCc001306; Mon, 8 Jul 2002 14:17:15 -0600 (MDT) (envelope-from stable@jnielsen.net) Message-ID: <00fb01c226bc$7b049440$0900a8c0@max> From: "John Nielsen" To: "Pete Carah" , Cc: References: <200207081952.g68JqB55059730@ns.altadena.net> Subject: Re: Hang problem with spamass-milter... Date: Mon, 8 Jul 2002 14:17:27 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL version=2.20 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Pete Carah wrote: > I have spamass-milter compiled and running in a fresh 4.6-stable > box (built last week). If two mail messages arrive "close enough" in > time, spamc hangs hard (needs kill -9 to stop it) in pipe-read state > with spamass-milter in pipe-read also. I have a suspicion about > read acting non-blocking in the pipe case; looking through the > pthread_read.c source, as long as EWOULDBLOCK or EAGAIN work right > things shouldn't act like this. > > Do these work right on pipes in thread context? I guess I could set > up a test program... > > Note that spamc is not compiled thread-safe (not required here since > it is started for each message). > > spamass-milter's configure does not make the right choices for freebsd; > I presume the port fixes this (I did so myself, adding _THREAD_SAFE and > -pthread). The C++ library may or may not be thread-safe? > > I saw a query about this same thing dated last Feb (looking at the > code fragment, I suspect it was in the same program); it is > still around. > > The hint at a fix then was "are you sure you are writing anything". > Given that the identical code works fine in debian, I suspect a system > problem. To me it appears to be the behavior of EWOULDBLOCK/EAGAIN with > pipes in thread context. I don't have any answers, but I can confirm the problem. I installed spamass-milter from the port, and it hangs every morning at 3:00 (when daily run output comes in from my other machines). I'd love to see a fix... :) JN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message