[Bug 470696] Review Request: rubygem-passenger - Passenger Ruby on Rails deployment system

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=470696

--- Comment #101 from Hongli Lai <honglilai at gmail.com> 2011-12-01 12:39:38 EST ---
If I remember correctly it was Debian. It's very important to me that lock()
handles EINTR. I don't think couching it with #ifdefs is a good idea though
because compiling a whitelist or blacklist is just too much work. Even in the
same OS, some versions of the threading library may be broken while some
versions may not, and later versions may introduce regressions. It's just
easier to always check for EINTR.

While it is technically correct that returning EINTR indicates a bug in the OS,
relying on the OS vendor to fix the bug is not a good practical solution.
- Different vendors fix bugs at different paces. Fixing the bug can take months
or years but the user wants the software to work yesterday. He does not care
which party is to blame.
- Some users use old versions of an OS by choice.
- Some users are part of an organization whose IT department does not allow OS
upgrades, for whatever reason.
- Upgrading Phusion Passenger is far easier than upgrading the entire OS and is
less risky.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.