From owner-freebsd-current@FreeBSD.ORG Fri Nov 14 13:19:29 2003 Return-Path: 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 2EF3016A4CE for ; Fri, 14 Nov 2003 13:19:29 -0800 (PST) Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3197B43FAF for ; Fri, 14 Nov 2003 13:19:28 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.12.8/8.12.3) with ESMTP id hAELJPaG011962; Fri, 14 Nov 2003 13:19:26 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200311142119.hAELJPaG011962@beastie.mckusick.com> To: Matt Smith In-Reply-To: Your message of "Fri, 14 Nov 2003 08:33:06 GMT." <3FB49342.3000404@xtaz.co.uk> Date: Fri, 14 Nov 2003 13:19:25 -0800 From: Kirk McKusick cc: freebsd-current@freebsd.org Subject: Re: HEADS-UP new statfs structure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2003 21:19:29 -0000 > Date: Fri, 14 Nov 2003 08:33:06 +0000 > From: Matt Smith > To: Marco Wertejuk > Cc: Kirk McKusick , freebsd-current@freebsd.org > Subject: Re: HEADS-UP new statfs structure > X-ASK-Info: Whitelist match > > Marco Wertejuk wrote: > > Just for a short note: cfsd (ports/security/cfs) should be > > recompiled as well after those statfs changes. > > > > And mail/postfix and devel/gnomevfs2 (ones's i've found so far) > > postfix did this every time it received a mail until I recompiled it: > > pid 4049 (smtpd), uid 1003: exited on signal 11 > > And gnomevfs was something I saw in another headsup. There are bound to > be others, I'm just keeping an eye on my /var/log/messages to see if > anything else sig 11 or 12's! So far so good though. > > Matt. This is why we make this change now so that it will be in place for the masses when 5.2 is released :-) Kirk McKusick