Date: Sun, 9 Apr 2000 07:02:43 -0400 From: Chris Johnson <cjohnson@palomine.net> To: Guy Helmer <ghelmer@cs.iastate.edu>, questions@freebsd.org Subject: Re: cron's complaint Message-ID: <20000409070242.A41930@palomine.net>
next in thread | raw e-mail | index | archive | help
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. > > > > > Meanwhile, I'd really like to know how to get cron working without > > > drowning me in hundreds of errors. I've rebooted since it started, and > > > the errors are still being churned out. It feels like something's been > > > changed permanently. > > > > I made some cosmetic edits to the active lines in /etc/crontab and cron > > stopped reporting those errors from that moment on. Later on, root > > dutifully sent me my StarTrek Night reminder email courtesy of cron, > > with no complaints. > > > > Probably all that was significant was that the file was changed and > > therefore re-read by cron. Might a corrupted crontab file in var cause this? > > Damn, I should have kept a copy. My personal crontab was mucking up > > too, but I'll have to wait until tomorrow before its jobs are due again. > > Hmm, a crontab file that triggers this activity would be a great data point... One box of mine just started doing this, running 3.4-STABLE as of March 24. The box ran for two weeks before it started doing it, though, and at the time the messages started it was (perhaps coincidentally) doing a buildworld. Before the buildworld, it had been very lightly loaded. The messages started at 2:05AM, i.e. right after the daily run stuff ran. I opened root's crontab file, which was empty (actually, it didn't exist at all and crontab created a new one), added a comment to it and saved it, opened it back up and removed the comment and saved it, and the messages stopped right away. Let me know if there's any other information I can provide. Chris 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?20000409070242.A41930>