From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200411160556.iAG5upJ05532@augusta.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? 
In-Reply-To: Your message of "Mon, 15 Nov 2004 23:44:22 EST."
	<200411160444.iAG4iMJ05266@augusta.math.psu.edu> 
Date: Tue, 16 Nov 2004 00:56:51 -0500
From: Dan Cross <cross@math.psu.edu>
Topicbox-Message-UUID: 024f7e4a-eace-11e9-9e20-41e7f4b1d025

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.