From owner-freebsd-ports@FreeBSD.ORG  Wed Aug 18 15:01:49 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AE8441065672
	for <freebsd-ports@freebsd.org>; Wed, 18 Aug 2010 15:01:49 +0000 (UTC)
	(envelope-from bounces@nabble.com)
Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158])
	by mx1.freebsd.org (Postfix) with ESMTP id 8BD3F8FC18
	for <freebsd-ports@freebsd.org>; Wed, 18 Aug 2010 15:01:45 +0000 (UTC)
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <bounces@nabble.com>) id 1Oljub-0006WZ-KU
	for freebsd-ports@freebsd.org; Wed, 18 Aug 2010 07:46:41 -0700
Message-ID: <29472170.post@talk.nabble.com>
Date: Wed, 18 Aug 2010 07:46:41 -0700 (PDT)
From: jyalavarti <jyalavarti@yahoo.com>
To: freebsd-ports@freebsd.org
In-Reply-To: <19409.58999.623809.616876@jerusalem.litteratus.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: jyalavarti@yahoo.com
References: <19409.58999.623809.616876@jerusalem.litteratus.org>
X-Mailman-Approved-At: Wed, 18 Aug 2010 15:44:31 +0000
Subject: Re: revisiting Spamassassin problem
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Aug 2010 15:01:49 -0000


Running sa-update fixed the problem for me. Did not dig much.

Cheers!
J.


Robert Huff wrote:
> 
> 
> 	Back in February there was a thread - "spamassassin problem
> with upgrade" - about spamd failing to start with this error:
> 
> child process [76967] exited or timed out without signaling production of
> a PID file: exit 255 at /usr/local/bin/spamd line 2588.
> /usr/local/etc/rc.d/sa-spamd: WARNING: failed to start spamd
> 
> 	The thread offered no definite solution except to downgrade.
> 	Is this still the case?
> 
> 
> 					Robert Huff
> 
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
> 
> 

-- 
View this message in context: http://old.nabble.com/revisiting-Spamassassin-problem-tp28344852p29472170.html
Sent from the freebsd-ports mailing list archive at Nabble.com.