From owner-freebsd-stable@FreeBSD.ORG  Fri Feb 13 05:31:30 2015
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3E5D38D5
 for <freebsd-stable@freebsd.org>; Fri, 13 Feb 2015 05:31:30 +0000 (UTC)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com
 [IPv6:2607:f8b0:400d:c04::22b])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id E81757AB
 for <freebsd-stable@freebsd.org>; Fri, 13 Feb 2015 05:31:29 +0000 (UTC)
Received: by mail-qg0-f43.google.com with SMTP id i50so11743131qgf.2
 for <freebsd-stable@freebsd.org>; Thu, 12 Feb 2015 21:31:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:date:message-id:subject:from:to:content-type;
 bh=hd4ixtzNu+FxkKsSPC98h8CzgcFVNRH62IcT5yXd7Rk=;
 b=xSBDw07due4L/6G05n2uL+2wdtrAyCEF45RBLVR/S0aXBBuE6WX/8wD3VxUDzEUBoC
 PqxZlNEXHxaSwLDGsAG0+m0Unn3/KzZu9LhAJNxIu003lMzZbIljsE0spWpe36up6Twl
 eNLaeY8YtUoVCjFEP9leQfC6jTw1zRyXEl6mHYtx99XIzk7VJ6CtQKPH/rMqIIzcov9M
 hy8/0xYYAuxDWm5EnW02WZOkmMvsGSOIUcrqAAm6BMtbtZ7NFDFX3jNTTIWF6GUaJ1bC
 tNuU7vhI5vxIy9PUT2Xe35kL69ICv3qSYwTurUcu94jI0PtnWVmTtjmgGnB+/uUPLu9D
 7IGA==
MIME-Version: 1.0
X-Received: by 10.140.22.234 with SMTP id 97mr18505801qgn.21.1423805488848;
 Thu, 12 Feb 2015 21:31:28 -0800 (PST)
Sender: geeohgeegeeoh@gmail.com
Received: by 10.96.76.199 with HTTP; Thu, 12 Feb 2015 21:31:28 -0800 (PST)
Date: Fri, 13 Feb 2015 15:31:28 +1000
X-Google-Sender-Auth: pz0ciwm2R6nenDRpevhp_wW7qxo
Message-ID: <CAM2GGy=Dkn5dhTcZtZApC=u7GnS87M5YD7KAtUjBqG7Y1KjFcw@mail.gmail.com>
Subject: freebsd-update 10.0p5 ->10.1 hits chflags or other problems on
 libc.so and init
From: George Michaelson <ggm@pobox.com>
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 05:31:30 -0000

Whats the right path out, when freebsd-update barfs on chflags for files?

I've been hit by libc.so and /sbin/init being barfed.

This is possibly the second time. I have about 15 hosts to do, holding off
the rest until I understand the risks.

(simple searches don't show a fix, but do show back history of
freebsd-update sometimes coming unstuck on this kind of thing)

-G