Could you cheat and create /opt2/puppetlabs and a symlink
from /opt/puppetlabs -> /opt2/puppetlabs before installation?
Otherwise, you can likely unpack the rpm, and futz with it,
but I could imagine that /opt/puppetlabs is buried in a
binary or two and thus awkward to change.
Hope that helps -
Hi Josh - thanks for the info.
Can I make an assertion that having the default read timeout be unlimited
is a mistake? In practical terms, anything over 60 seconds means
something is broken.
Could I suggest (without having to go and update the bug because I'm a
bad bad lazy person) that along
I couldn't find any reference to this different behaviour, so I'm
wondering if anyone knows if this is intentional.
I use a bunch of defined types, and with the future parser, when I refer
to a variable in a template, it seems that the default scope is not the
scope of the class.
e.g. in a
| I'm running Puppet master version 2.7.9 on RHEL6. My puppet agent is
| 2.7.5 on RHEL5. I have an issue where I get the following email every
| 30 mins even though no changes were detected by puppet agent.
That sounds like this:
http://projects.puppetlabs.com/issues/9167
That issue report
