From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 02:58:41 2014 Return-Path: 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 ED876FF; Wed, 12 Nov 2014 02:58:41 +0000 (UTC) Received: from mario.brtsvcs.net (mario.brtsvcs.net [IPv6:2607:fc50:0:a400::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5FFB7E2; Wed, 12 Nov 2014 02:58:41 +0000 (UTC) Received: from chombo.houseloki.net (c-71-59-211-166.hsd1.or.comcast.net [71.59.211.166]) by mario.brtsvcs.net (Postfix) with ESMTPSA id AE3F52C160F; Wed, 12 Nov 2014 02:58:39 +0000 (UTC) Received: from [IPv6:2601:7:2580:674:baca:3aff:fe83:bd29] (ivy.libssl.so [IPv6:2601:7:2580:674:baca:3aff:fe83:bd29]) by chombo.houseloki.net (Postfix) with ESMTPSA id 82BAC21B; Tue, 11 Nov 2014 18:58:37 -0800 (PST) Message-ID: <5462CCDC.7070202@bluerosetech.com> Date: Tue, 11 Nov 2014 18:58:36 -0800 From: Darren Pilgrim Reply-To: freebsd-stable@freebsd.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Glen Barber Subject: Re: Request for r261231 backport to 10.0 References: <545EAE7E.60009@bluerosetech.com> <20141111205545.GU1236@hub.FreeBSD.org> In-Reply-To: <20141111205545.GU1236@hub.FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2014 02:58:42 -0000 On 11/11/2014 12:55 PM, Glen Barber wrote: > On Sat, Nov 08, 2014 at 03:59:58PM -0800, Darren Pilgrim wrote: >> 10.0 i386 introduced a bug in cron that results in it running jobs at the >> wrong time[1]. r261231[2] MFC'd the fix to 10-stable, but after 10.0-R. >> 10.1 is due in a few days, but it will be at least a month before move to >> 10.1 because I wait a bit for problems that tend to crop up only after >> release. >> >> Building cron from stable/10 r261231 and copying it over /usr/sbin/cron on >> my 10.0 systems fixes the issue, but that's an evil hack. >> >> Can we get this backported to 10.0 as an errata fix? >> > > Once RE gets 10.1-RELEASE out, we'll begin work on an EN for 10.0 for > this issue. Thank you!