Thanks, In a few hours, I will change the TZ and update the
/etc/cron.d/automc with the real hours in UTC. This will be much better!
Dave
On 06/13/2017 01:11 PM, Kevin A. McGrail wrote:
FYI
-------- Forwarded Message --------
Subject: Re: [Bug 7432] Update cron jobs on sa-vm1 to run at UTC and
ignore daylight savings change
Date: Tue, 13 Jun 2017 10:33:19 -0700
From: Chris Lambertus <c...@apache.org>
To: Kevin A. McGrail <kevin.mcgr...@mcgrail.com>
CC: Apache Infrastructure <infrastruct...@apache.org>
You can change it. Puppet is supposed to update it to UTC, but I have
seen a few circumstances where this isn't happening on 16.04.
On Jun 11, 2017, at 6:12 PM, Kevin A. McGrail
<kevin.mcgr...@mcgrail.com <mailto:kevin.mcgr...@mcgrail.com>> wrote:
Question, on sa-vm1, can we change the machine to UTC or do we need a
Jira ticket?
-------- Forwarded Message --------
Subject: [Bug 7432] Update cron jobs on sa-vm1 to run at UTC and
ignore daylight savings change
Date: Sun, 11 Jun 2017 16:45:36 +0000
From: bugzilla-dae...@issues.apache.org
Reply-To: sysadmins@spamassassin.apache.org
To: sysadmins@spamassassin.apache.org
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7432
Dave Jones<da...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |da...@apache.org
--- Comment #1 from Dave Jones<da...@apache.org> ---
It would be nice to run the server at UTC to solve this problem and not have to
keep calculating file timestamp offsets when we run 'ls -l'. We would need to
run this past the INFRA team. I think they have Puppet managing the timezone
file but I am not sure. We may want to try to change the system timezone to
UTC and see if Puppet puts it back to "America/Los_Angeles" then open a Jira
issue to ask the INFRA team about running the server at UTC.
--
You are receiving this mail because:
You are the assignee for the bug.