Qmail
[Top] [All Lists]

Re: Is saferead not really safe on Solaris 8?

To: qmail@list.cr.yp.to
Subject: Re: Is saferead not really safe on Solaris 8?
From: Jorge Valdes <jvaldes@intercom.com.sv>
Date: Fri, 24 Nov 2006 15:56:28 -0600
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
In-reply-to: <20061124.191156.02469879.hanche@math.ntnu.no>
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
Organization: Intercom El Salvador
References: <20061124.191156.02469879.hanche@math.ntnu.no>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.666
Harald Hanche-Olsen wrote:
We are seeing some qmail-smtpd processes hanging for days on end.  If
truss is to be believed, they all hang in a read() on stdin, that is,
on a socket read.

Now this should not be possible, because qmail-smtpd uses saferead() on
all network reads, and saferead first calls select() and then read()
only if select() indicates that there is data to be read.  Surely, if
select() said there is data, then read() cannot hang?

So I begin to suspect an OS bug.  Has anybody else seen this?

- Harald
Me too. Solaris 9.
I have a script that kills off qmail-smtpd processes that have been running over 24 hours, since they just appear to do nothing other than to occupy tcpserver slots (annoying). I run a cron job once a day ~4am localtime and have had no complaints, but I haven't really given it serious consideration until now.

--
Jorge Valdes



<Prev in Thread] Current Thread [Next in Thread>