Debian bug report logs - #1105 , boring messages ----------------------------------------------------------------------- Message sent to debian-devel@pixar.com: Subject: Bug#1105: Problems with `cron' Reply-To: iwj10@cus.cam.ac.uk (Ian Jackson), debian-bugs@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: Sat, 15 Jul 1995 14:48:01 GMT Resent-Message-ID: X-Debian-PR-Package: cron X-Debian-PR-Keywords: Received: via spool for debian-bugs; Sat, 15 Jul 1995 14:48:01 GMT Received: with rfc822 via encapsulated-mail id 071514355722357; Sat, 15 Jul 1995 14:35:57 GMT 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 (Debian /\oo/\ Smail3.1.29.1 #29.32); Sat, 15 Jul 95 12:49 BST Message-Id: Date: Sat, 15 Jul 95 12:49 BST From: iwj10@cus.cam.ac.uk (Ian Jackson) To: Debian bugs submission address 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. ----------------------------------------------------------------------- Message sent: From: iwj10@thor.cam.ac.uk (Ian Jackson) To: iwj10@cus.cam.ac.uk (Ian Jackson) Subject: Bug#1105: Acknowledgement (was: Problems with `cron') In-Reply-To: References: 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#1105" or "Re: Bug#1105" so that we can identify it as relating to the same problem. 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. Ian Jackson (maintainer, debian-bugs) ----------------------------------------------------------------------- Message sent to debian-devel@pixar.com: Subject: Bug#1105: Problems with `cron' Reply-To: andrew@kryten.it.com.au (Andrew Howell), debian-bugs@pixar.com Resent-To: debian-devel@pixar.com Resent-From: andrew@kryten.it.com.au (Andrew Howell) Resent-Sender: iwj10@cus.cam.ac.uk Resent-Date: Sun, 16 Jul 1995 13:03:08 GMT Resent-Message-ID: X-Debian-PR-Package: cron X-Debian-PR-Keywords: Received: via spool for debian-bugs; Sun, 16 Jul 1995 13:03:08 GMT Received: with rfc822 via encapsulated-mail id 071612593721904; Sun, 16 Jul 1995 12:59:37 GMT 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 (Debian /\oo/\ Smail3.1.29.1 #29.33); Sun, 16 Jul 95 18:12 WST Message-Id: From: andrew@kryten.it.com.au (Andrew Howell) To: iwj10@cus.cam.ac.uk, debian-bugs@pixar.com Date: Sun, 16 Jul 1995 18:12:16 +0800 (WST) In-Reply-To: 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 sent: From: iwj10@thor.cam.ac.uk (Ian Jackson) To: andrew@kryten.it.com.au (Andrew Howell) Subject: Bug#1105: Info received (was Bug#1105: Problems with `cron') In-Reply-To: References: Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developers to accompany the original report. If you wish to continue to submit further information on your problem, please do the same thing again: send it to debian-bugs@pixar.com, ensuring that the Subject line starts with "Bug#1105" or "Re: Bug#1105" so that we can identify it as relating to the same problem. 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. Ian Jackson (maintainer, debian-bugs) ----------------------------------------------------------------------- Message sent: From: iwj10@thor.cam.ac.uk (Ian Jackson) To: Ian Jackson In-Reply-To: References: Subject: Bug#1105: marked as done (was: Problems with `cron') Your message dated Sun, 29 Oct 95 19:28 GMT with message-id and subject line Bug#1105: Problems with `cron' has caused the attached bug report to be marked as done. It is your now responsibility to ensure that the bug report is dealt with. (NB: If you are a system administrator and have no idea what I'm talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Ian Jackson (maintainer, debian-bugs) Received: with rfc822 via encapsulated-mail id 071514355722357; Sat, 15 Jul 1995 14:35:57 GMT From cus.cam.ac.uk!iwj10 Sat Jul 15 06:24:54 1995 Return-Path: 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 (Debian /\oo/\ Smail3.1.29.1 #29.32); Sat, 15 Jul 95 12:49 BST Message-Id: Date: Sat, 15 Jul 95 12:49 BST From: iwj10@cus.cam.ac.uk (Ian Jackson) To: Debian bugs submission address 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. ----------------------------------------------------------------------- Message sent: From: iwj10@thor.cam.ac.uk (Ian Jackson) To: iwj10@cus.cam.ac.uk (Ian Jackson) Subject: Bug#1105 acknowledged by developer (was: Problems with `cron') References: In-Reply-To: This is an automatic notification regarding your bug report. Responsibility for it has been taken by one of the developers, namely Ian Jackson . You should be hearing from them with a substantive response shortly, if you have not already done so. If not, please contact them directly, or email debian-bugs@pixar.com or myself. Ian Jackson (maintainer, debian-bugs) ----------------------------------------------------------------------- Ian Jackson / iwj10@thor.cam.ac.uk , with the debian-bugs tracking mechanism This page last modified 07:43:01 GMT Wed 01 Nov