Bug#33171: marked as done (cron has gone to UTC time?)
Your message dated Thu, 13 May 1999 09:47:24 -0700
with message-id <v04205106b360b142e04a@[206.163.71.146]>
and subject line Fixed in 2.1.1 and later.
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Ian Jackson
(administrator, Debian bugs database)
Received: (at submit) by bugs.debian.org; 10 Feb 1999 08:41:25 +0000
Received: (qmail 27305 invoked from network); 10 Feb 1999 08:41:24 -0000
Received: from kite.kitenet.net (HELO kitenet.net) (qmailr@209.157.80.18)
by master.debian.org with SMTP; 10 Feb 1999 08:41:24 -0000
Received: (qmail 8721 invoked by uid 500); 10 Feb 1999 08:40:21 -0000
Date: Wed, 10 Feb 1999 00:40:21 -0800
From: Joey Hess <joey@kitenet.net>
To: submit@bugs.debian.org, Kai Henningsen <kaih@khms.westfalen.de>
Cc: debian-devel@lists.debian.org
Subject: Re: cron has gone to UTC time?
Message-ID: <19990210004021.T27306@kitenet.net>
Mail-Followup-To: submit@bugs.debian.org,
Kai Henningsen <kaih@khms.westfalen.de>,
debian-devel@lists.debian.org
References: <19990206155752.A10191@neuromancer.hou.aspentech.com> <Pine.LNX.3.96.990206203523.20583A-100000@wakko> <7ActB1J1w-B@khms.westfalen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.12i
In-Reply-To: <7ActB1J1w-B@khms.westfalen.de>; from Kai Henningsen on Wed, Feb 10, 1999 at 09:29:00AM +0200
Package: timezones
Kai Henningsen wrote:
> But it doesn't stay that way all the time when you upgrade timezones.
> Happened to me yesterday.
Aha! I had suspicions thing might be it buy hadn't tracked it down.
> I think this counts as a timezones bug.
I agree.
> Scenario:
>
> unpack cron
> unpack timezones - this deletes (!!) /etc/timezone
> setup cron - cron is now at UTC
> setup timezones - a correct /etc/timezone is recreated
>
> This means that during a timezones upgrade, there is a window when the
> system is running under UTC. During a mass upgrade, this window can be
> fairly long.
>
>
> MfG Kai
--
see shy jo
Reply to: