Issue #9228 has been updated by Jesse Peterson.
It would seem this would have to work going back many versions in Mac OS X lest things like `sudo -u` simply wouldn't be possible. Unless of course I'm missing something about how setting UID/EUID works. Could it have been a Ruby bug perhaps? In any case no worries. I'm manually patching gem installations at the moment until a release is complete. Thanks! ---------------------------------------- Bug #9228: Darwin (Mac OS X) excepted from changing UID, GID https://projects.puppetlabs.com/issues/9228 Author: Jesse Peterson Status: Accepted Priority: High Assignee: Category: exec Target version: 2.7.x Affected Puppet version: 2.7.3 Keywords: euid uid egid gid darwin macosx Branch: I'm unsure why, but it seems like Puppet thinks it's not possible to set the UID or GID via Process.uid= on Darwin/Mac OS X. Unfortunately this severely impacts the Exec type when user => or group => is set. Because lots of things execute through the bash shell bash will revert the euid (setting it back to the real uid) if it's different than the uid, making the euid setting almost useless. By applying the supplied patch things work as expected. I'm not sure the history of why Puppet was doing this but it appears to work fine with it. This is Puppet 2.7.3 on Mac OS X 10.6.8 using the Mac's built-in Ruby 1.8.7-pl174. See also #8770 for related discussion and less related but similar issue in #374. -- 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://projects.puppetlabs.com/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.
