I've also just received a similar email from cron.
Return-Path: [email protected]
Delivery-Date: Tue Mar 29 07:30:01 2011
Return-Path: <[email protected]>
X-Original-To: root
Delivered-To: [email protected]
Received: by orac.inputplus.co.uk (Postfix, from userid 0)
id 2BCF1327A6; Tue, 29 Mar 2011 07:30:01 +0100 (BST)
From: [email protected] (Cron Daemon)
To: [email protected]
Subject: Cron <root@orac> start -q anacron || :
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env:
<PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Message-Id: <[email protected]>
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.
** Changed in: anacron (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
start: Job is already running: anacron
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
