Debian bug report logs - #377
cron on notebooks (was Re: admin packages moved)

Package: cron?; Reported by: iwj10@cus.cam.ac.uk (Ian Jackson); 138 days old.

Message received at debian-bugs:


From cus.cam.ac.uk!iwj10 Thu Feb  2 03:48:52 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0ra01r-00061sC; Thu, 2 Feb 95 03:48 PST
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA24734
  (5.65c/IDA-1.4.4 for <debian-bugs@pixar.com>); Thu, 2 Feb 1995 03:49:22 -0800
Received: by bootes.cus.cam.ac.uk 
	(Smail-3.1.29.0 #24) id m0rZzzB-000BzlC; Thu, 2 Feb 95 11:46 GMT
Received: by chiark (Smail3.1.28.1 #3)
	id m0rZTsW-0002g8Z; Wed, 1 Feb 95 01:29 GMT
Message-Id: <m0rZTsW-0002g8Z.ijackson@nyx.cs.du.edu>
Date: Wed, 1 Feb 95 01:29 GMT
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: Debian bugs submission address <debian-bugs@pixar.com>
Cc: Matt Birkholz <birkholz@primenet.com>
Subject: cron on notebooks (was Re: admin packages moved)
In-Reply-To: <m0rZCPW-0005RBC@dagobah.primenet.com>
References: <m0rYjUI-0002g8Z.ijackson@nyx.cs.du.edu>
	<m0rZCPW-0005RBC@dagobah.primenet.com>

Package: cron?

(I'm filing this as a bug as I think it should be fixed ...)

Matt Birkholz writes ("admin packages moved"):
> Making the vixie cron daemon notebook-friendly is going to be a bit of a
> problem.  One of its features is that it stat's its spool directory once a
> minute to detect changes to crontab files.  Thus, the crontab command
> doesn't have to signal the daemon; it just bumps the modtime of the spool
> directory.[ref third paragraph of the cron(8) manpage.]

Well, experimentation shows that stat() doesn't change the access time
on a directory, so it shouldn't dirty the inode.

> I'm guessing this is why my disk never spins down.  (Actually, I don't see
> why the inode for the spool directory doesn't stay in the buffer cache...)

It certainly should.  I suggest that something else on your system is
regularly dirtying inodes.  Do you have `at' installed ?

Try removing the crontab line for atrun and see what happens then.

Ian.

Message sent:


From: iwj@cam-orl.co.uk (Ian Jackson)
To: iwj10@cus.cam.ac.uk (Ian Jackson)
Subject: Bug#377: Acknowledgement (was: cron on notebooks (was Re: admin packages moved))
In-Reply-To: <m0rZTsW-0002g8Z.ijackson@nyx.cs.du.edu>
References: <m0rZTsW-0002g8Z.ijackson@nyx.cs.du.edu>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
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.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#377" or "Re: Bug#377" so that
we can identify it as relating to the same problem.

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

Ian Jackson
(maintainer, debian-bugs)


Message sent to debian-devel@pixar.com:


Subject: Bug#377: cron on notebooks (was Re: admin packages moved)
Reply-To: iwj10@cus.cam.ac.uk (Ian Jackson), debian-bugs-done@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: iwj10@cus.cam.ac.uk (Ian Jackson)
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Thu, 02 Feb 1995 12:03:03 GMT
Resent-Message-ID: <debian-bugs-handler.377.020211502112208@pixar.com>
X-Debian-PR-Package: cron?
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Thu, 02 Feb 1995 12:03:03 GMT
Received: with rfc822 via encapsulated-mail id 020211502112208;
          Thu, 02 Feb 1995 11:50:22 GMT
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0ra01r-00061sC; Thu, 2 Feb 95 03:48 PST
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA24734
  (5.65c/IDA-1.4.4 for <debian-bugs@pixar.com>); Thu, 2 Feb 1995 03:49:22 -0800
Received: by bootes.cus.cam.ac.uk
	(Smail-3.1.29.0 #24) id m0rZzzB-000BzlC; Thu, 2 Feb 95 11:46 GMT
Received: by chiark (Smail3.1.28.1 #3)
	id m0rZTsW-0002g8Z; Wed, 1 Feb 95 01:29 GMT
Message-Id: <m0rZTsW-0002g8Z.ijackson@nyx.cs.du.edu>
Date: Wed, 1 Feb 95 01:29 GMT
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: Debian bugs submission address <debian-bugs@pixar.com>
Cc: Matt Birkholz <birkholz@primenet.com>
In-Reply-To: <m0rZCPW-0005RBC@dagobah.primenet.com>
References: <m0rYjUI-0002g8Z.ijackson@nyx.cs.du.edu>
	<m0rZCPW-0005RBC@dagobah.primenet.com>

Package: cron?

(I'm filing this as a bug as I think it should be fixed ...)

Matt Birkholz writes ("admin packages moved"):
> Making the vixie cron daemon notebook-friendly is going to be a bit of a
> problem.  One of its features is that it stat's its spool directory once a
> minute to detect changes to crontab files.  Thus, the crontab command
> doesn't have to signal the daemon; it just bumps the modtime of the spool
> directory.[ref third paragraph of the cron(8) manpage.]

Well, experimentation shows that stat() doesn't change the access time
on a directory, so it shouldn't dirty the inode.

> I'm guessing this is why my disk never spins down.  (Actually, I don't see
> why the inode for the spool directory doesn't stay in the buffer cache...)

It certainly should.  I suggest that something else on your system is
regularly dirtying inodes.  Do you have `at' installed ?

Try removing the crontab line for atrun and see what happens then.

Ian.


Ian Jackson / iwj10@thor.cam.ac.uk, with the debian-bugs tracking mechanism
This page last modified 06:43:02 GMT Wed 21 Jun