On Thu, Sep 23, 2010 at 12:35 AM, qutic development <mailingli...@qutic.com> wrote: > Jeff, > > thank you for your answer. But my question was not about exec. The question > was how to set the path for every "system" command puppet is executing ;-)
Ah, I see, my misunderstanding. > It seems to be that on Nexenta the path is not set the right way. The path > in /etc/profile is fine, but this might be not recognized by executing the > system command out of the ruby puppet code. This isn't really a right / wrong or solaris / linux "way" but rather a general issue of setting the PATH for the process and making sure it's exported to sub processes. Depending on how you run puppet (cron, or init.d) just set and export PATH the way you want it in that location as Felix mentioned. -Jeff -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
