From: Dan Cross <cross@math.psu.edu>
To: Russ Cox <russcox@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Weird timeout thing in smtpd?
Date: Tue, 16 Nov 2004 16:09:35 -0500 [thread overview]
Message-ID: <200411162109.iAGL9ZJ08233@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Tue, 16 Nov 2004 07:31:15 EST." <ee9e417a041116043130abf42@mail.gmail.com>
Russ Cox <russcox@gmail.com> writes:
>
> > So, the question is: what would cause send to take a *really* long
> > time? I mean, on the order of seconds.... And, more to the point,
> > how can I fix that?
>
> run send by hand and then run acid on it and look around. ;-)
Following Russ's suggestion, we discovered that send was hanging
out waiting for /mail/lib/qmail to finish, which was in turn waiting
on runq. On systems with backlogged mail, runq can take a long time
to complete. Running runq in the background makes the problem go
away. The fix is now on sources.
- Dan C.
prev parent reply other threads:[~2004-11-16 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 2:07 Dan Cross
2004-11-16 2:15 ` Russ Cox
2004-11-16 2:35 ` Dan Cross
2004-11-16 4:44 ` Dan Cross
2004-11-16 5:56 ` Dan Cross
2004-11-16 12:31 ` Russ Cox
2004-11-16 21:09 ` Dan Cross [this message]
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=200411162109.iAGL9ZJ08233@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).