Issue #3013 has been updated by Ricky Zhou.
Markus Roberts wrote: > Belay that pessimism. I think if we combine the child termination trap with > the eof trap there may be a sane (if somewhat recondite) way to thread this > needle. I'll try to code it up and report back. Ugh. I spent the last hour trying to think up solutions with SIGCHLD handlers, select, and other fun. Unfortunately, one problem I don't think we can avoid is that even if we manage to prevent the indefinite blocking read, as soon as we close the read end of the pipe and the misbehaved daemon tries to write anything to stdout (the write end), it will get a SIGPIPE (and probably get terminated as a result). ---------------------------------------- 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.
