From owner-freebsd-current Thu Mar 28 14:15:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA11618 for current-outgoing; Thu, 28 Mar 1996 14:15:18 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA11603 for ; Thu, 28 Mar 1996 14:14:54 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id JAA17796; Fri, 29 Mar 1996 09:04:27 +1030 From: Michael Smith Message-Id: <199603282234.JAA17796@genesis.atrad.adelaide.edu.au> Subject: Re: /etc/localtime and screensaver? To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 29 Mar 1996 09:04:26 +1030 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <199603280849.JAA23698@uriah.heep.sax.de> from "J Wunsch" at Mar 28, 96 09:49:29 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > > > This is actually expected behavior. The same things happens to me when > > I run ntptime on my laptop after being away for awhile. Basically, the > > time has changed enough so that sometimes cron jobs start up because the > > system time is really hosed up. > > That's why one should normally kill cron before changing the time, and > restart it then. I must say that I was of the impression that the Vixie cron we're using was smart enough to deal with that sort of thing - certainly I've never had any problems with it getting upset... > cheers, J"org -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[