From owner-freebsd-bugs Fri Mar 3 8:50: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 381D637B64C for ; Fri, 3 Mar 2000 08:50:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA36441; Fri, 3 Mar 2000 08:50:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Fri, 3 Mar 2000 08:50:04 -0800 (PST) Message-Id: <200003031650.IAA36441@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Guy Helmer Subject: Re: bin/17134: problem with cron forgetting jobs Reply-To: Guy Helmer Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/17134; it has been noted by GNATS. From: Guy Helmer To: Sheldon Hearn Cc: tshansen@nlanr.net, FreeBSD-gnats-submit@FreeBSD.ORG, Guy Helmer Subject: Re: bin/17134: problem with cron forgetting jobs Date: Fri, 3 Mar 2000 10:41:45 -0600 (CST) On Fri, 3 Mar 2000, Sheldon Hearn wrote: > On Thu, 02 Mar 2000 12:40:45 PST, Todd Hansen wrote: > > > Anyway, the problem is related to what was mentioned in > > bin/6004. Except we have more information and a greater need to work > > with you to figure this out. > > Guy Helmer closed that PR because he couldn't get any more information > from the originator. I'm copying him on this mail in the hopes that > he was actually interested in that PR. :-) I closed 6004 since I was neither able to verify that it was still a problem nor obtain further clues. I am suprised that more people have not encountered this problem if it is simply exhibited with frequently-executed jobs. I will try running cron with some debugging options enabled (-x proc and maybe some others), and see if I can duplicate this; if anyone else wants to do so also, that's fine :-) It may be helpful to obtain a core dump and executable image from from a cron daemon built with "cd /usr/src/usr.sbin/cron && make CFLAGS=-g LDFLAGS=-static clean all" -- then run cron and "kill -6" it after it has started to exhibit this behavior. The bug's cause could be a stray pointer or an off-by-one error, but seeing what was in the data structures may help. Guy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message