Issue #3013 has been updated by Markus Roberts.

New branch up, with my best approximation of a solution.  After researching the 
osirid problem (our worst known case) and such similar bug reports as google 
provides an inquirer, it appears that the SIGPIPE problem is not likely to be 
an issue.  Most daemons do not retain the caller's STDOUT, and those do 
generally do not write to it (they retain it as an oversight, not with the 
intention to use it).  Daemon that retain the caller's STDOUT and attempt o 
write to it after the caller has ceased to exist without checking for the 
possible failure (if any exist) would generally be considered buggy to the 
point that we may be forgiven for not accommodating them.

Get the branch here & try it and/or see the dev-list for the commit and any 
ensuing discussion.

-- Markus

P.S. If anyone has access to a Debian Etch box and would be willing to try and 
reproduce the osirid problem, I would be very interested in the results.
----------------------------------------
Bug #3013: util.rb:execute broken on Ruby <1.8.3
http://projects.reductivelabs.com/issues/3013

Author: Ricky Zhou
Status: Ready for Testing
Priority: Urgent
Assigned to: Markus Roberts
Category: exec
Target version: 0.25.3
Affected version: 0.25.2
Keywords: 
Branch: http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/3013


Apparently the patch in ticket #2731 introduced one more issue by using 
readpartial, which isn't available until ruby 1.8.3 (RHEL4 at least is 
affected).  I'm not sure how this is normally handled in ruby, but if the 
readpartial function is not available, the code should fall back to sysread 
(along with some code for handling EINTR).

Anybody with better ruby knowledge know how this should be done?


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to