version of Puppet?
On Wed, Nov 13, 2013 at 9:58 AM, Stefan Pommerening p...@dmsp.dejavascript:
wrote:
Hi there,
I'm totally stuck with the following (cross-platform) problem:
- I use a custom type as exported resource which is being 'filled-in' on
Linux servers
and this type should
content between
puppetmaster on Linux and puppet agent on Windows is working correctly.
Am Donnerstag, 14. November 2013 00:14:06 UTC+1 schrieb jcbollinger:
On Wednesday, November 13, 2013 9:58:53 AM UTC-6, Stefan Pommerening wrote:
Hi there,
I'm totally stuck with the following (cross
SOLVED!
My (dumb) problem was that I did not start the command window (on Windows
server) using the right-click 'Administrator', but I used my own account
which generally IS an account with full privileges but Windows seems to
need the real thing...
Unfortunately there is absolute NO error
Hi there,
I'm totally stuck with the following (cross-platform) problem:
- I use a custom type as exported resource which is being 'filled-in' on
Linux servers
and this type should be realized / created by some ruby provider on a
Windows server.
Puppet on Linux and Windows is always 2.7.19.
Hi Wolf,
indeed that 'exec' solution is what I've found when searching for a
solution.
In my situation this won't help - unfortunately.
Nevertheless I tracked down the main problem to be caused by different
usage scenarios for yum.
When upgrading I have to specify only the main varnish package
Hi all,
I am trying to use puppet (2.7.18) for downgrading varnish cache on Centos
Linux (6.3).
Unfortunately there are two varnish RPMs (which seem to have circular
dependencies):
varnish-3.0.4-1.el6.x86_64
varnish-libs-3.0.4-1.el6.x86_64
When using ensure for downgrading I get a bunch of
Hi all,
I am currently writing a graylog2 module for puppet on centos 6.3 and
need to update Ruby on target machine to 1.9.3 although there is already
an older version (1.8.7) installed.
Therefore I decided to use rvm but for writing a more general puppet module
I need to invoke commands like
