Hi Felix,
Thanks for the reply.
Yep - that snippet is representative. I've copied the full thing for you
below. Granted, it needs some tidying up, but I think it should just work
as it stands:
class app::reservations {
include tomcat
Exec {
path => "/usr/bin:/usr/sbin:/bin:/sbin:/usr/loca
I should probably add that, for $reasons, I'm using Puppet 3.6.1.
On Sunday, 19 July 2015 15:07:39 UTC+1, Andrew Langhorn wrote:
>
> Hi Felix,
>
> Thanks for the reply.
>
> Yep - that snippet is representative. I've copied the full thing for you
> below. Granted, it needs some tidying up, but I t
On Sun, Jul 19, 2015 at 7:07 AM, Andrew Langhorn <
andrew.langh...@digital.cabinet-office.gov.uk> wrote:
> Hi Felix,
>
> Thanks for the reply.
>
> Yep - that snippet is representative. I've copied the full thing for you
> below. Granted, it needs some tidying up, but I think it should just work
>
Hi,
something I noticed when trying a simple puppetserver setup.
I installed puppetserver from PC1 on a Debian 7 box (will try Debian 8
once PC1 has puppetserver for it) and just started the service. It fails
like this:
Exception in thread "main" java.lang.IllegalStateException: Cannot
initializ
I don't know why, but when I renamed the class, things started to work.
Very odd. Maybe I should just upgrade to the latest stable 3.x release
(3.8.0, I think), or even 4.
Thanks though - especially helpful on this list, as usual :)
On 19 July 2015 at 19:54, Peter Huene wrote:
> On Sun, Jul 19,
El 17/07/15 a las 09:31, bjoern pohl escribió:
Hi,
we're currently transforming some ugly perl-based management scripts
(which placed some config data on the client and then configured
something with it) to puppet.
While it is definitely the best idea point to keep all that config data
on the ma
