<strong>Report forwarded</strong> to <code>debian-bugs-dist@lists.debian.org, shaleh@debian.org (Sean E. Perry)</code>:<br>
<code>Bug#49029</code>; Package <code>anacron</code>.


debian-bugs-dist@lists.debian.orgshaleh@debian.org (Sean E. Perry)

Subject: Bug#49029: anacron: Anacron could run jobs at times system load is low.
Reply-To: Arjan Drieman <duckie@node0911.a2000.nl>, 49029@bugs.debian.org
Resent-From: Arjan Drieman <duckie@node0911.a2000.nl>
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: shaleh@debian.org (Sean E. Perry)
Resent-Date: Tue, 02 Nov 1999 19:33:00 GMT
Resent-Message-ID: <handler.49029.B.9415710648424@bugs.debian.org>
Resent-Sender: owner@bugs.debian.org
X-Debian-PR-Message: report 49029
X-Debian-PR-Package: anacron
X-Debian-PR-Keywords: 
X-Loop: owner@bugs.debian.org
Received: via spool by bugs@bugs.debian.org id=B.9415710648424
          (code B ref -1); Tue, 02 Nov 1999 19:33:00 GMT
Date: Tue, 2 Nov 1999 20:30:51 +0100
Message-Id: <199911021930.UAA05351@node0911.a2000.nl>
From: Arjan Drieman <duckie@node0911.a2000.nl>
To: submit@bugs.debian.org
X-Mailer: bug 3.2.6

Package: anacron
Version: N/A
Severity: wishlist

Rob Reid, author for The Linux Gazette, wrote a script for use of cron on computers that aren't on very ofen, just like anacron.
(http://linuxgazette.nllgg.nl/issue47/reid.html)

After pointing Rob at anacron, he wrote me:

> I prefer groundskeeper, since it optimizes a slightly different criterion:

> groundskeeper will make sure that the commands are run at convienient times 
> for the users as closely to the specified intervals as machine uptime permits.

> i.e. batch puts the job off until the CPU is able to handle it without
> disrupting whatever the users are doing in the foreground.  Anacron's only
> advantage over groundskeeper is that if the computer is only on for a time
> less than groundskeeper's check interval (say, a laptop on the subway going 
> into work) it would run the jobs while groundskeeper would miss its chance.
> But if I turned on a computer for such a brief period, I probably WOULDN'T
> want it to spend that time doing cron jobs.

He has a good point. Maybe something like this could be implemented in anacron?

-- System Information
Debian Release: potato
Kernel Version: Linux node0911 2.2.13 #1 Fri Oct 22 06:19:49 CEST 1999 i486 unknown




<strong>Acknowledgement sent</strong> to <code>Arjan Drieman &lt;duckie@node0911.a2000.nl&gt;</code>:<br>
New Bug report received and forwarded.  Copy sent to <code>shaleh@debian.org (Sean E. Perry)</code>.


-t

From: owner@bugs.debian.org (Debian Bug Tracking System)
To: Arjan Drieman <duckie@node0911.a2000.nl>
Subject: Bug#49029: Acknowledgement (anacron: Anacron could run jobs at times system load is low.)
Message-ID: <handler.49029.B.9415710648424.ack@bugs.debian.org>
In-Reply-To: <199911021930.UAA05351@node0911.a2000.nl>
References: <199911021930.UAA05351@node0911.a2000.nl>
X-Debian-PR-Message: ack 49029

Thank you for the problem report you have sent regarding Debian.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers mailing list for
their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 shaleh@debian.org (Sean E. Perry)

If you wish to submit further information on your problem, please send
it to 49029@bugs.debian.org (and *not* to
bugs@bugs.debian.org).

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.

Darren Benham
(administrator, Debian Bugs database)



Received: (at submit) by bugs.debian.org; 2 Nov 1999 19:31:04 +0000
Received: (qmail 8319 invoked from network); 2 Nov 1999 19:30:57 -0000
Received: from spartacus.a2000.nl (HELO smtp2.a2000.nl) (62.108.1.20)
  by master.debian.org with SMTP; 2 Nov 1999 19:30:57 -0000
Received: from node0911.a2000.nl ([62.108.9.17])
	by smtp2.a2000.nl with esmtp (Exim 2.02 #4)
	id 11ijds-0005Cf-00
	for submit@bugs.debian.org; Tue, 2 Nov 1999 20:30:52 +0100
Received: (from duckie@localhost)
	by node0911.a2000.nl (8.9.3/8.9.3/Debian 8.9.3-6) id UAA05351;
	Tue, 2 Nov 1999 20:30:51 +0100
Date: Tue, 2 Nov 1999 20:30:51 +0100
Message-Id: <199911021930.UAA05351@node0911.a2000.nl>
From: Arjan Drieman <duckie@node0911.a2000.nl>
Subject: anacron: Anacron could run jobs at times system load is low.
To: submit@bugs.debian.org
X-Mailer: bug 3.2.6

Package: anacron
Version: N/A
Severity: wishlist

Rob Reid, author for The Linux Gazette, wrote a script for use of cron on computers that aren't on very ofen, just like anacron.
(http://linuxgazette.nllgg.nl/issue47/reid.html)

After pointing Rob at anacron, he wrote me:

> I prefer groundskeeper, since it optimizes a slightly different criterion:

> groundskeeper will make sure that the commands are run at convienient times 
> for the users as closely to the specified intervals as machine uptime permits.

> i.e. batch puts the job off until the CPU is able to handle it without
> disrupting whatever the users are doing in the foreground.  Anacron's only
> advantage over groundskeeper is that if the computer is only on for a time
> less than groundskeeper's check interval (say, a laptop on the subway going 
> into work) it would run the jobs while groundskeeper would miss its chance.
> But if I turned on a computer for such a brief period, I probably WOULDN'T
> want it to spend that time doing cron jobs.

He has a good point. Maybe something like this could be implemented in anacron?

-- System Information
Debian Release: potato
Kernel Version: Linux node0911 2.2.13 #1 Fri Oct 22 06:19:49 CEST 1999 i486 unknown




<strong>Information forwarded</strong> to <code>debian-bugs-dist@lists.debian.org, shaleh@debian.org (Sean E. Perry)</code>:<br>
<code>Bug#49029</code>; Package <code>anacron</code>.


debian-bugs-dist@lists.debian.orgshaleh@debian.org (Sean E. Perry)

Subject: Bug#49029: anacron: Anacron could run jobs at times system l
Reply-To: "Sean 'Shaleh' Perry" <shaleh@via.net>, 49029@bugs.debian.org
Resent-From: "Sean 'Shaleh' Perry" <shaleh@via.net>
Orignal-Sender: shaleh@one.willcodeforfood.via.net
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: shaleh@debian.org (Sean E. Perry)
Resent-Date: Tue, 02 Nov 1999 20:18:01 GMT
Resent-Message-ID: <handler.49029.B.9415731703094@bugs.debian.org>
Resent-Sender: owner@bugs.debian.org
X-Debian-PR-Message: report 49029
X-Debian-PR-Package: anacron
X-Debian-PR-Keywords: 
X-Loop: owner@bugs.debian.org
Received: via spool by bugs@bugs.debian.org id=B.9415731703094
          (code B ref -1); Tue, 02 Nov 1999 20:18:01 GMT
Message-ID: <XFMail.991102120555.shaleh@via.net>
X-Mailer: XFMail 1.3.1 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199911021930.UAA05351@node0911.a2000.nl>
Date: Tue, 02 Nov 1999 12:05:55 -0700 (PST)
Sender: shaleh@one.willcodeforfood.via.net
From: "Sean 'Shaleh' Perry" <shaleh@via.net>
To: Arjan Drieman <duckie@node0911.a2000.nl>
Cc: submit@bugs.debian.org

Dunno.  Personally, I have my crontab set so that if I am on battery, my
(ana)cron jobs never run.  So, until i plug my laptop in, I do not have to
worry about it.

Frankly, on a laptop as long as the job runs sometime, I do not really see the
point in caring.  However, I will read his article (Linux Gazette is a nice
little magazine).  Will see.



<strong>Acknowledgement sent</strong> to <code>&quot;Sean 'Shaleh' Perry&quot; &lt;shaleh@via.net&gt;</code>:<br>
Extra info received and forwarded to list.  Copy sent to <code>shaleh@debian.org (Sean E. Perry)</code>.


-t

From: owner@bugs.debian.org (Debian Bug Tracking System)
To: "Sean 'Shaleh' Perry" <shaleh@via.net>
Subject: Bug#49029: Info received (was Bug#49029: anacron: Anacron could run jobs at times system l)
Message-ID: <handler.49029.B.9415731703094.ackinfo@bugs.debian.org>
In-Reply-To: <XFMail.991102120555.shaleh@via.net>
References: <XFMail.991102120555.shaleh@via.net>
X-Debian-PR-Message: ack-info-maintonly 49029

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developer(s) and
to the developers mailing list to accompany the original report.

Your message has been sent to the package maintainer(s):
 shaleh@debian.org (Sean E. Perry)

If you wish to continue to submit further information on your problem,
please send it to 49029@bugs.debian.org, as before.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.

Darren Benham
(administrator, Debian Bugs database)



Received: (at submit) by bugs.debian.org; 2 Nov 1999 20:06:10 +0000
Received: (qmail 2797 invoked from network); 2 Nov 1999 20:05:59 -0000
Received: from mail.via.net (209.81.9.4)
  by master.debian.org with SMTP; 2 Nov 1999 20:05:59 -0000
Received: from shaleh@one.willcodeforfood.via.net [209.81.29.202] (HELO one.willcodeforfood.via.net)
	by mail.via.net (8.9.3/8.9.3) via ESMTP
	id <MAA25654-shaleh@via.net>;
	Tue, 2 Nov 1999 12:05:57 -0800 (PST)
Message-ID: <XFMail.991102120555.shaleh@via.net>
X-Mailer: XFMail 1.3.1 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199911021930.UAA05351@node0911.a2000.nl>
Date: Tue, 02 Nov 1999 12:05:55 -0700 (PST)
Sender: shaleh@one.willcodeforfood.via.net
From: "Sean 'Shaleh' Perry" <shaleh@via.net>
To: Arjan Drieman <duckie@node0911.a2000.nl>
Subject: RE: Bug#49029: anacron: Anacron could run jobs at times system l
Cc: submit@bugs.debian.org

Dunno.  Personally, I have my crontab set so that if I am on battery, my
(ana)cron jobs never run.  So, until i plug my laptop in, I do not have to
worry about it.

Frankly, on a laptop as long as the job runs sometime, I do not really see the
point in caring.  However, I will read his article (Linux Gazette is a nice
little magazine).  Will see.