Issue #3013 has been updated by Markus Roberts.
Yeah. There's a reason they put up the huge "Abandon all hope" sign over this stuff. As for the SIGPIPE problem, I'm thinking that daemons writing to stdout is frowned upon, but that isn't a solution it's just shifting the blame. My SIGCHLD idea and a half dozen variation have all gotten nowhere, with the complications you'd expect and one I hadn't thought of, at least explicitly: we aren't dealing with the OS directly and some of the cleverer tricks also run afoul of ruby's assumptions. I haven't exhausted all the permutations, but one way or another I'm going to run out of options before to much longer. ---------------------------------------- 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.
