From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] cron, again
Date: Mon, 19 Jun 2006 16:04:52 -0600 [thread overview]
Message-ID: <14ec7b180606191504w2b9a455fr6ae49274ff2da8d7@mail.gmail.com> (raw)
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.
next reply other threads:[~2006-06-19 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 22:04 andrey mirtchovski [this message]
2006-06-19 22:07 ` geoff
2006-06-19 22:13 ` Francisco J Ballesteros
2006-06-19 22:23 ` andrey mirtchovski
2006-06-19 22:27 ` andrey mirtchovski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14ec7b180606191504w2b9a455fr6ae49274ff2da8d7@mail.gmail.com \
--to=mirtchovski@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).