On Fri, Aug 03, 2001 at 03:07:57PM +0100, Richard Underwood wrote:
Hi,
I asked about qmail-remote processes hanging in read() on this list
a few days ago. It appears that this has been reported before, but no
conclusion seemed to have been made.
I just looked at the server I had
On Sat, Jun 09, 2001 at 06:32:55AM -0400, Troy Settle wrote:
Yes, I've had qmail-remote processes sit there for weeks. I think that
instead of killing them off wholesale, I'll pick one or two processes and
see just how long they'll hang around. I'll post weekly updates if there's
any
One more time,
I did tcpdump and strace on stuck qmail-remote for over an hour.
strace shows that qmail-remote is stuck on: 'read(3', and tcpdump shows
that nothing comes in.
On Fri, Jun 08, 2001 at 03:13:54PM +, Mark wrote:
processed those 1500 messages in less than 30 minutes. However,
On Fri, Jun 08, 2001 at 09:47:16PM +, Mark wrote:
Then it's an OS bug.
qmail-remote only gets to the read() if the OS (via select() ) says
that the read will not block. Ergo, the OS is lying.
If it's OS bug, anybody heard/knows of such severe network related
bug in RedHat 6.2?
What
Hello,
I encountered very veird problem with qmail-remote hanging
indefinitelly (for over 2 weeks). Here are the details:
qmail-remote stays in ESTABLESHED state forever.
strace show that qmail-remote hangs doing: 'read(3,'
Most of hanged qmail remote are trying to deliver to outblaze.com
(or
