From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <14ec7b180606191504w2b9a455fr6ae49274ff2da8d7@mail.gmail.com> Date: Mon, 19 Jun 2006 16:04:52 -0600 From: "andrey mirtchovski" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [9fans] cron, again Topicbox-Message-UUID: 6d16f1d8-ead1-11e9-9d60-3106f5b1d025 did we fix cron? did the changes made it in? i have a machine which went bananas today and it's a few hundred kilometers from here so i can't really debug. for the brief moments that it's up, i see that cron is trying to start waaaaaaay too many jobs: bananas Jun 19 15:56:01 upas: called /bin/upas/runq -a /mail/queue /mail/lib/remotemail on bananas.plan9.ca bananas Jun 19 15:56:01 upas: called /bin/upas/runq -a /mail/queue /mail/lib/remotemail on bananas.plan9.ca bananas Jun 19 15:56:01 upas: called /bin/upas/runq -a /mail/queue /mail/lib/remotemail on bananas.plan9.ca bananas Jun 19 15:56:01 upas: called /bin/upas/runq -a /mail/queue /mail/lib/remotemail on bananas.plan9.ca bananas Jun 19 15:56:01 upas: called /bin/upas/runq -a /mail/queue /mail/lib/remotemail on bananas.plan9.ca bananas Jun 19 15:56:01 upas: called /bin/upas/runq -a /mail/queue /mail/lib/remotemail on bananas.plan9.ca bananas Jun 19 15:56:01 upas: called /bin/upas/runq -a /mail/queue /mail/lib/remotemail on bananas.plan9.ca bananas Jun 19 15:56:01 upas: called /bin/upas/runq -a /mail/queue /mail/lib/remotemail on bananas.plan9.ca a few thousand of those will bring the machine down. there is aparrently no trigger, as i can trace through the log: cron starts every minute as usual, until (with no change in system time, which used to trigger it before) it will go bonkers next iteration. the machine hangs and eventually reboots itself so i'm not really able to do any debugging, but i'll try anyway. let me know if you have a fix hidden somewhere.