From owner-freebsd-ports@FreeBSD.ORG  Fri Apr 23 19:06:41 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3FBE9106564A
	for <ports@freebsd.org>; Fri, 23 Apr 2010 19:06:41 +0000 (UTC)
	(envelope-from jtrigg@spamcop.net)
Received: from azure.heraldsnet.org
	(static-71-178-19-94.washdc.fios.verizon.net [71.178.19.94])
	by mx1.freebsd.org (Postfix) with ESMTP id 1A8588FC12
	for <ports@freebsd.org>; Fri, 23 Apr 2010 19:06:41 +0000 (UTC)
Received: by static-71-178-19-94.washdc.fios.verizon.net (Postfix,
	from userid 1001)
	id 6FC7911431; Fri, 23 Apr 2010 14:49:04 -0400 (EDT)
Date: Fri, 23 Apr 2010 14:49:04 -0400
From: Jim Trigg <jtrigg@spamcop.net>
To: Robert Huff <roberthuff@rcn.com>
Message-ID: <20100423184904.GE9863@spamcop.net>
Mail-Followup-To: Robert Huff <roberthuff@rcn.com>, ports@freebsd.org,
	scheidell@secnap.net
References: <19409.58999.623809.616876@jerusalem.litteratus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19409.58999.623809.616876@jerusalem.litteratus.org>
User-Agent: Mutt/1.4.2.3i
Cc: ports@freebsd.org, scheidell@secnap.net
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: Fri, 23 Apr 2010 19:06:41 -0000

On Fri, Apr 23, 2010 at 02:27:03PM -0400, 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?

When I've seen that, it's meant that I needed to run sa-update to rebuild
the rule database (I think it is).

Jim
-- 
Jim Trigg, Lord High Everything Else  O-      /"\
                                              \ /  ASCII RIBBON CAMPAIGN
Hostmaster, Huie Kin family website            X    HELP CURE HTML MAIL
Verger, All Saints Church - Sharon Chapel     / \