Date: Sat, 8 Apr 2000 08:11:51 +0930 (CST) From: Justin Hawkins <justin@tardis.mx.com.au> To: Guy Helmer <ghelmer@cs.iastate.edu> Cc: Sue Blake <sue@welearn.com.au>, Sheldon Hearn <sheldonh@uunet.co.za>, freebsd-questions@FreeBSD.ORG Subject: Re: cron's complaint Message-ID: <Pine.BSF.4.21.0004080809110.23275-100000@gw.tardis.mx.com.au> In-Reply-To: <Pine.HPX.4.05.10004040816250.28738-100000@popeye.cs.iastate.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0004080809110.23275-100000>