Note how my local time is 07:30:01, exactly the same as François
Marier's email when he opened the bug.
BTW, to the 24 people that said this bug was also affecting them, it
helps to change the status from New to Confirmed. :-) Until a bug
moves off of New there's often no work done on fixing it since it has
just been reported by one person.
I've also just received a similar email from cron.
Return-Path: <email address hidden> co.uk (Postfix, from userid 0) ANSI_X3. 4-1968 usr/local/ sbin:/usr/ local/bin: /sbin:/ bin:/usr/ sbin:/usr/ bin>
Delivery-Date: Tue Mar 29 07:30:01 2011
Return-Path: <email address hidden>
X-Original-To: root
Delivered-To: <email address hidden>
Received: by orac.inputplus.
id 2BCF1327A6; Tue, 29 Mar 2011 07:30:01 +0100 (BST)
From: <email address hidden> (Cron Daemon)
To: <email address hidden>
Subject: Cron <root@orac> start -q anacron || :
Content-Type: text/plain; charset=
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Message-Id: <email address hidden>
Date: Tue, 29 Mar 2011 07:30:01 +0100 (BST)
start: Job is already running: anacron
Note how my local time is 07:30:01, exactly the same as François
Marier's email when he opened the bug.
BTW, to the 24 people that said this bug was also affecting them, it
helps to change the status from New to Confirmed. :-) Until a bug
moves off of New there's often no work done on fixing it since it has
just been reported by one person.