Debian bug report logs - #1105
Problems with `cron'

Message received at debian-bugs-done:

From chiark.chu.cam.ac.uk!ian Sun Oct 29 11:29:40 1995
Return-Path: <ian@chiark.chu.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t9dQK-0006F1C; Sun, 29 Oct 95 11:29 PST
Received: from artemis.chu.cam.ac.uk by pixar.com with SMTP id AA14298
  (5.67b/IDA-1.5 for debian-bugs-done-pipe@mongo.pixar.com); Sun, 29 Oct 1995 11:29:12 -0800
Received: from chiark.chu.cam.ac.uk by artemis.chu.cam.ac.uk with smtp
	(Smail3.1.29.1 #33) id m0t9dP6-0007uQC; Sun, 29 Oct 95 19:28 GMT
Received: by chiark.chu.cam.ac.uk
	id m0t9dOw-0002bdC
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Sun, 29 Oct 95 19:28 GMT
Message-Id: <m0t9dOw-0002bdC@chiark.chu.cam.ac.uk>
Date: Sun, 29 Oct 95 19:28 GMT
From: Ian Jackson <ian@chiark.chu.cam.ac.uk>
To: andrew@kryten.it.com.au (Andrew Howell),
        Debian bugs acknowledgements <debian-bugs-done@pixar.com>
Subject: Re: Bug#1105: Problems with `cron'
In-Reply-To: <m0t9R53-000AZZC@kryten.it.com.au>
References: <m0t9NEA-0002bdC@chiark.chu.cam.ac.uk>
	<m0t9R53-000AZZC@kryten.it.com.au>

Andrew Howell writes ("Re: Bug#1105: Problems with `cron'"):
> Ian Jackson writes:
> > The problem hasn't happened to me for a long time; I think it is
> > probably fixed.  If you haven't seen it either I propose to close this
> > bug report.
> 
> Yeah I haven't seen it for a long time.

Right, I'll close it, thanks.

Ian.

Message received at debian-bugs:

From kryten.it.com.au!andrew Sun Jul 16 05:58:28 1995
Return-Path: <andrew@kryten.it.com.au>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sXTHA-00065gC; Sun, 16 Jul 95 05:58 PDT
Received: from kryten.it.com.au by pixar.com with SMTP id AA22376
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sun, 16 Jul 1995 05:56:49 -0700
Received: by kryten.it.com.au
	id <m0sXQgL-000AgyC@kryten.it.com.au>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Sun, 16 Jul 95 18:12 WST
Message-Id: <m0sXQgL-000AgyC@kryten.it.com.au>
From: andrew@kryten.it.com.au (Andrew Howell)
Subject: Re: Bug#1105: Problems with `cron'
To: iwj10@cus.cam.ac.uk, debian-bugs@pixar.com
Date: Sun, 16 Jul 1995 18:12:16 +0800 (WST)
In-Reply-To: <m0sX5iP-0000YIZ@chiark.al.cl.cam.ac.uk> from "Ian Jackson" at Jul 15, 95 12:49:00 pm
X-Mailer: ELM [version 2.4 PL24 PGP2]
Content-Type: text
Content-Length: 1119      

> 
> Package: cron
> Version: 3.0pl1-18
> 
> I seem to be having a problem with cron getting `stuck'.  It's not
> clear what happens, but the symptoms are that no cron jobs run until
> cron is killed and restarted.
> 
> Possible culprits are the kernel (I recently changed to 1.3.1), GCC
> 2.6.3 (my previous cron package was compiled using 2.5.2) and syslogd
> (of which I'm running version 1.2-9).
> 
> If noone else has seen similar symptoms I shall try experimenting, and
> might try reverting to a 1.2.x kernel or recompiling cron with
> debugging enabled so I can make and use a coredump.

This has happened to me a number of times, though not recently, maybe
a month ago.

Andrew

-----------------------------------------------------------------------
Dehydration - 34%, Recollection of previous evening - 2%, embarrassment
factor - 91%.  Advise repair schedule:- off line for 36 hours, re-boot
startup disk, and replace head - wow, what a night!
                -- Kryten in Red Dwarf `The Last Day'

Andrew Howell				               andrew@it.com.au 
Perth, Western Australia		      howellaa@cs.curtin.edu.au 

Message received at debian-bugs:

From cus.cam.ac.uk!iwj10 Sat Jul 15 06:24:54 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sX7DB-0007uDC; Sat, 15 Jul 95 06:24 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA21561
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 15 Jul 1995 06:23:20 -0700
Received: by bootes.cus.cam.ac.uk 
	(Smail-3.1.29.0 #36) id m0sX7Ck-000BzmC; Sat, 15 Jul 95 14:24 BST
Received: by chiark
	id <m0sX5iP-0000YIZ@chiark.al.cl.cam.ac.uk>
	(Debian /\oo/\ Smail3.1.29.1 #29.32); Sat, 15 Jul 95 12:49 BST
Message-Id: <m0sX5iP-0000YIZ@chiark.al.cl.cam.ac.uk>
Date: Sat, 15 Jul 95 12:49 BST
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: Debian bugs submission address <debian-bugs@pixar.com>
Subject: Problems with `cron'

Package: cron
Version: 3.0pl1-18

I seem to be having a problem with cron getting `stuck'.  It's not
clear what happens, but the symptoms are that no cron jobs run until
cron is killed and restarted.

Possible culprits are the kernel (I recently changed to 1.3.1), GCC
2.6.3 (my previous cron package was compiled using 2.5.2) and syslogd
(of which I'm running version 1.2-9).

If noone else has seen similar symptoms I shall try experimenting, and
might try reverting to a 1.2.x kernel or recompiling cron with
debugging enabled so I can make and use a coredump.

Ian.