From owner-freebsd-bugs Sat Aug 25 23: 0: 6 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8921637B403 for ; Sat, 25 Aug 2001 23:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f7Q602J18718; Sat, 25 Aug 2001 23:00:02 -0700 (PDT) (envelope-from gnats) Date: Sat, 25 Aug 2001 23:00:02 -0700 (PDT) Message-Id: <200108260600.f7Q602J18718@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mike Barcroft Subject: Re: bin/17134: problem with 3.0-RELEASE cron forgetting jobs Reply-To: Mike Barcroft Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/17134; it has been noted by GNATS. From: Mike Barcroft To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: bin/17134: problem with 3.0-RELEASE cron forgetting jobs Date: Sun, 26 Aug 2001 01:58:44 -0400 Adding to Audit-Trail. ----- Forwarded message from Todd Hansen ----- Delivered-To: mike@freebsd.org X-Authentication-Warning: mave.nlanr.net: tshansen owned process doing -bs Date: Mon, 6 Aug 2001 08:59:01 -0700 (PDT) From: Todd Hansen To: mike@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org, tonym@nlanr.net Subject: Re: bin/17134: problem with 3.0-RELEASE cron forgetting jobs In-Reply-To: <200107220012.f6M0Cmg21052@freefall.freebsd.org> I have forgotten how far we tested, maybe tony knows. I think we tested with 4.0 cron? I know we stopped playing with the bug well before 4.3 was released. We were never able to find a version which did not exhibit the bug. However, the problem was very rare and we can only see it because of the number of machines we are running. I don't know if we have seen the bug recently though. -todd ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message