From owner-freebsd-stable@FreeBSD.ORG Mon Jun 30 11:18:43 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFC399EA for ; Mon, 30 Jun 2014 11:18:43 +0000 (UTC) Received: from mail.ultra-secure.de (mail.ultra-secure.de [88.198.178.88]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F25AF2A6C for ; Mon, 30 Jun 2014 11:18:42 +0000 (UTC) Received: (qmail 60413 invoked by uid 89); 30 Jun 2014 11:18:37 -0000 Received: by simscan 1.4.0 ppid: 60408, pid: 60410, t: 0.1363s scanners: attach: 1.4.0 clamav: 0.97.3/m:55/d:19142 Received: from unknown (HELO suse3.ewadmin.local) (rainer@ultra-secure.de@212.71.117.1) by mail.ultra-secure.de with ESMTPA; 30 Jun 2014 11:18:37 -0000 Date: Mon, 30 Jun 2014 13:18:31 +0200 From: Rainer Duffner To: freebsd-stable@freebsd.org Subject: Re: Hourly cron jobs running to early Message-ID: <20140630131831.1b89e52a@suse3.ewadmin.local> In-Reply-To: <2035F53FC8C246469D6927696ED288D3@Rivendell> References: <2035F53FC8C246469D6927696ED288D3@Rivendell> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.22; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2014 11:18:43 -0000 Am Mon, 30 Jun 2014 13:53:51 +0300 schrieb "Reko Turja" : > -----Original Message----- > From: Spil Oss > Sent: Monday, June 30, 2014 12:04 PM > > > A system I manage that was recently upgraded from 9 to 10.0 and to a > > later version of VMWare vSphere (5.5U1) is no longer running hourly > > jobs at the top of the hour but just before. This is especially > > Do you have the file present in /etc (wall_cmos_clock) that tells the > system that the HW clock is not running UTC? BTW: what is one supposed to configure for a VMware-guest? Is the HW clock running UTC or not? Does it depend on the vmware-host?