From owner-freebsd-questions Fri Apr 7 15:44:18 2000 Delivered-To: freebsd-questions@freebsd.org Received: from tardis.mx.com.au (tardis.mx.com.au [203.34.34.73]) by hub.freebsd.org (Postfix) with ESMTP id 5231537BA98 for ; Fri, 7 Apr 2000 15:44:10 -0700 (PDT) (envelope-from justin@tardis.mx.com.au) Received: from localhost (justin@localhost) by tardis.mx.com.au (8.9.3/8.9.3) with ESMTP id IAA23583; Sat, 8 Apr 2000 08:11:52 +0930 (CST) (envelope-from justin@tardis.mx.com.au) Date: Sat, 8 Apr 2000 08:11:51 +0930 (CST) From: Justin Hawkins To: Guy Helmer Cc: Sue Blake , Sheldon Hearn , freebsd-questions@FreeBSD.ORG Subject: Re: cron's complaint In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Guy Helmer wrote: > On Tue, 4 Apr 2000, Sue Blake wrote: > > > On Tue, Apr 04, 2000 at 09:35:35PM +1000, Sue Blake wrote: > > > On Tue, Apr 04, 2000 at 12:33:35PM +0200, Sheldon Hearn wrote: > > > > On Tue, 04 Apr 2000 18:05:44 +1000, Sue Blake wrote: > > > > > > > > > CRON in malloc(): warning: pointer to wrong page. > > > > > CRON in free(): warning: pointer to wrong page. > > Hmm, a crontab file that triggers this activity would be a great data > point... > > My working hypothesis has been that the memory corruption problems in cron > are due to signals and malloc library re-entrancy (as was the case with > inetd(8)). I have changed cron in the same way inetd(8) was changed in rev > 1.44. I am interested in having people try the changes to see if they fix > these and other related problems. I too have had this problem, seemingly not related to the contents of the crontab file, as for me, a kill and restart of the cron process cured it. I have had it reoccur a couple of times since then, but the restart always fixes it. Running 3.4-STABLE, about 2 months old. - Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message