From: Dan Cross <cross@math.psu.edu>
To: 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 00:56:51 -0500 [thread overview]
Message-ID: <200411160556.iAG5upJ05532@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Mon, 15 Nov 2004 23:44:22 EST." <200411160444.iAG4iMJ05266@augusta.math.psu.edu>
Dan Cross <cross@math.psu.edu> writes:
> Hmm, a little more digging shows that it's hanging on reading the
> output of /bin/upas/send in data() in smtpd.c. I worked around that by
> only reading send's stderr output if status is non-zero. Moving
> beyond that, it seems to hang forever in proc_wait(), which is sort
> of strange. That would be, I think, waiting for send's exit status.
> This is a bit complex for me as I'm debugging this over SSH using
> ed, so the more productivly enhancing tools are unavailable at the
> moment.
Well, this is starting to make some sense. Send is taking a *really*
long time to do anything. I think what's happening is that send is
running so long that the client times out and spits out an error
message and resolves to retry later. However, on the server side,
send is still running, and eventually the mail gets delivered. At
some point, the client retries sending the mail, and send works
very quickly at that point, so the client is happy but a duplicate
message gets sent.
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?
- Dan C.
next prev parent reply other threads:[~2004-11-16 5:56 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 [this message]
2004-11-16 12:31 ` Russ Cox
2004-11-16 21:09 ` Dan Cross
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=200411160556.iAG5upJ05532@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).