From owner-freebsd-questions@FreeBSD.ORG Fri Nov 7 17:49:16 2014 Return-Path: Delivered-To: freebsd-questions@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 1B68DCD8 for ; Fri, 7 Nov 2014 17:49:16 +0000 (UTC) Received: from mario.brtsvcs.net (mario.brtsvcs.net [199.48.128.182]) (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 E992863C for ; Fri, 7 Nov 2014 17:49:15 +0000 (UTC) Received: from chombo.houseloki.net (c-73-37-112-64.hsd1.or.comcast.net [73.37.112.64]) by mario.brtsvcs.net (Postfix) with ESMTPSA id 205692C160F for ; Fri, 7 Nov 2014 17:49:08 +0000 (UTC) Received: from [IPv6:2601:7:2580:674:baca:3aff:fe83:bd29] (unknown [IPv6:2601:7:2580:674:baca:3aff:fe83:bd29]) by chombo.houseloki.net (Postfix) with ESMTPSA id 4A541FDD for ; Fri, 7 Nov 2014 09:49:06 -0800 (PST) Message-ID: <545D060F.40101@bluerosetech.com> Date: Fri, 07 Nov 2014 09:49:03 -0800 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: newsyslog oddity after upgrade to 10.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 17:49:16 -0000 I have a pair of servers with newsyslog.conf entries scheduling rotations daily or monthly (on the first), always at midnight. When the systems were running 9.3, newsyslog would rotate them at exactly midnight (the archive files would have timestamps of 00:00). After a freebsd-update upgrade to 10.0, newsyslog is indeed rotating late: timestamps of 00:58, for example, and the log contents cut off at about 1 am. The fields had been "$D0" or "$M1D0" in 9.3. When I saw this not working right in 10.0, I switched to "@T00" and "@01T00" instead to see if there was some kind of bug in the older format. The problem happens with either specification. It seemed oddly timed with the switch from Daylight Savings Time, so I reset both machines to UTC, rebooted them, confirmed they're running on UTC, but they both still do it.