I'm currently using this "hack" in a script I run (which also fires up Puppet)
to make sure my HOME path is available:
sed -i -e "s/'HOME', //"
#{$home}/.rbenv/versions/#{$ruby_version}/gemsets/global/gems/puppet-3.0.1/lib/puppet/util/posix.rb
This is where the removal of the HOME (and other)
Hey jwkoelewijn, do you mind posting your solution for the rabbitmq
provider.
Thanks!
On Monday, 8 October 2012 04:18:42 UTC-7, jwkoelewijn wrote:
>
> Thanks for this suggestion,
>
> this did the trick!
>
> Kind regards,
>
> J.W. Koelewijn
>
> On Thursday, October 4, 2012 4:24:26 PM UTC+2, jcbol
Thanks for this suggestion,
this did the trick!
Kind regards,
J.W. Koelewijn
On Thursday, October 4, 2012 4:24:26 PM UTC+2, jcbollinger wrote:
>
>
>
> On Wednesday, October 3, 2012 8:11:55 AM UTC-5, Daniele Sluijters wrote:
>>
>> Hi,
>>
>> Sorry, I got confused between two things. It's not the
On Wed, Oct 3, 2012 at 5:45 AM, Daniele Sluijters
wrote:
> Hello,
>
> In Puppet 3 Puppet does its absolute best to make sure $HOME, $USER and
> $LOGNAME environment variables are unset and nowhere to be found. I realise
> this change was necessary because it caused some weird start-up issues with
On Thu, Oct 4, 2012 at 7:24 AM, jcbollinger wrote:
>
>
> Puppet's guts have code for setting a custom environment for commands, but
> the 'command' and 'commands' functions don't provide an interface to it.
> I'm working from the code here, not actual experience, but it looks like you
> can use th
On Wednesday, October 3, 2012 8:11:55 AM UTC-5, Daniele Sluijters wrote:
>
> Hi,
>
> Sorry, I got confused between two things. It's not the actual Exec type.
> it's when a provider executes a command that the environment cannot be set.
>
>
Puppet's guts have code for setting a custom environment
Within a provider, I think you can use this syntax:
has_command(:port, "/opt/local/bin/port") do
environment :HOME => "/opt/local"
end
http://www.mail-archive.com/puppet-dev@googlegroups.com/msg17373.html
On Wednesday, October 3, 2012 9:11:03 AM UTC-4, jwkoelewijn wrote:
> Hi Stephen,
>
> Y
Hi Stephen,
You are right about the exec command being able to receive an environment
hash. This, however, does not solve our problem, because this is not
possible when creating a new Puppet Type and Provider. In the provider
commands are created using the "commands => 'system_command' " class
Hi,
Sorry, I got confused between two things. It's not the actual Exec type.
it's when a provider executes a command that the environment cannot be set.
--
Daniele Sluijters
On Wednesday, 3 October 2012 15:00:54 UTC+2, Stephen Gran wrote:
>
> Hi,
>
> On Wed, 2012-10-03 at 05:45 -0700, Daniele
Hi,
On Wed, 2012-10-03 at 05:45 -0700, Daniele Sluijters wrote:
> Hello,
>
>
> In Puppet 3 Puppet does its absolute best to make sure $HOME, $USER
> and $LOGNAME environment variables are unset and nowhere to be found.
> I realise this change was necessary because it caused some weird
> start-up
Hello,
In Puppet 3 Puppet does its absolute best to make sure $HOME, $USER and
$LOGNAME environment variables are unset and nowhere to be found. I realise
this change was necessary because it caused some weird start-up issues with
Puppet but this also killed our RabbitMQ module.
RabbitMQ is wr
11 matches
Mail list logo
