followup: stuck lmtpd processes

[Henrique de Moraes Holschuh]

On Wed, 24 Sep 2003, Rob Siemborski wrote:
> However, I have looked into this and to my surprise, Linux is indeed
> restarting the system calls instead of returning with EINTR.  However, the
> answer here is to set up the alarm() handler with sigaction without
> setting SA_RESTART, not to jump through select() hoops or make nonblocking
> lock attempts.

Yep, that's exactly it. Bullseye, Rob!

> I'll work on fixing fud shortly (its using signal() and it should be
> using sigaction()).

And I will do a linux fcntl/flock patch that uses alarm() WITHOUT
SA_RESTART as soon as I can.

> Linux should certainly be accomodated, but not in a way that causes
> *severe* performance penalties on operating systems that don't
> mysteriously fall asleep in the middle of a blocking flock() or fcntl()
> call.

Agreed.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh