From owner-freebsd-current@FreeBSD.ORG  Fri Mar 12 08:16:03 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8C95D16A4CE
	for <current@FreeBSD.org>; Fri, 12 Mar 2004 08:16:03 -0800 (PST)
Received: from port-212-202-51-138.reverse.qsc.de
	(port-212-202-51-138.reverse.qsc.de [212.202.51.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4CC8643D1D
	for <current@FreeBSD.org>; Fri, 12 Mar 2004 08:14:33 -0800 (PST)
	(envelope-from eikemeier@fillmore-labs.com)
Message-ID: <4051E016.5030303@fillmore-labs.com>
Date: Fri, 12 Mar 2004 17:06:46 +0100
From: Oliver Eikemeier <eikemeier@fillmore-labs.com>
Organization: Fillmore Labs GmbH - http://www.fillmore-labs.com/
MIME-Version: 1.0
To: Exim Users <exim-users@exim.org>,
	FreeBSD ports <ports@FreeBSD.org>,
	FreeBSD current <current@FreeBSD.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: KMail/1.5.9
Subject: FYI: Using exim after an upgrade from FreeBSD 5.1 to 5.2
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: FreeBSD ports <ports@FreeBSD.org>
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2004 16:16:03 -0000

Before this start to be a FAQ:

If you upgrade from FreeBSD 5.1 to 5.2, please do

	portupgrade -Rf 'exim-*'

Otherwise your symptoms may include entries in /var/log/exim/mainlog like:

  spool directory space check failed: space=0 inodes=0

This may be caused by the changes in the statfs structure,
see entry 20031112 in /usr/src/UPDATING:

 <http://cvsweb.freebsd.org/src/UPDATING?rev=1.282>

Regards
    Oliver
.