On Tuesday, January 28, 2014 6:02:09 AM UTC-8, jcbollinger wrote:
>
>
> You could try wrapping your task in a script that defers running it until
> the agent's lock file disappears. That would be cleaner and at least
> slightly more elegant.
>
>
Oh good point. That would be beyond my limited W
The fix I found for this is to schedule the task using an XML template with
the parameter specified (you can edit these settings under
Task Properties > Triggers > Edit > Advanced). The task repeats every
minute for 15 minutes after the start time.
The StartBoundary parameter is set to the ti
or me. It's ugly, but I'll
document it for reference.
> Regards,
> Felix
>
> On 01/27/2014 06:07 PM, elliott wrote:
> > Any ideas? The clients are all Windows, FWIW.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&q
I'm wondering if anyone knows a good way to get the date and time when a
portion of code in a Puppet manifest is actually *executed*. Sometimes my
manifests take a long time to run, and I need to schedule a task to occur
soon after the end of the run, no matter when that occurs.
I have tried
>
> Agreed, I'm puzzled why it's not named thus in the upstream module.
>
> Perhaps it's only suitable for specific puppet versions?
>
Okay, good enough for me :) So the standard practice then would be to
fully-qualify all classes, definitions and types declared within modules?
--
You recei
Hi guys,
I'm trying to use the Subversion module here:
https://github.com/duritong/puppet-subversion
I have unzipped it to my modules folder but I am having problems calling
the definitions from elsewhere in my manifests. I get the following error:
err: Could not retrieve catalog from remote
Hi,
I've been having trouble with this resource type on Solaris using the
packages from the OpenCSW repository.
Delving into the code, I've found that the operatingsystem fact isn't being
retrieved correctly by the parsed.rb code for the resource type. This
results in the default fields being us
Hi all, looking for some general advice for how people are doing
this...
We have some packages that *must* be kept at a particular version
(e.g. httpd, php) because our code and configurations depend on it.
As far as I'm aware, in puppet, the only parameter that can be passed
to a package type des
all was good.
Thanks for the help.
Cheers,
-elliott-
On Mar 22, 1:19 pm, Mohamed Lrhazi wrote:
> I use this pattern:
>
> [master]
>
> templatedir = /etc/puppet/environments/$environment/
> modulepath = /etc/puppet/environments/$environment/modules
> mani
Thanks Cody.
The client's environment does need to be set, either through the
puppet.conf or on the command line, but the environments also need to
be defined on the master, as far as I know.
On Mar 22, 12:46 pm, Cody Robertson wrote:
> On 03/22/2011 03:41 PM, ellio
Hi guys,
I've had separate development/testing environments partially working
for a while, in that modules get pulled from the correct per-
environment path. However, something that has never seemed to work
was a per-environment manifest. I have more need for this now so I'd
like to track it dow
Hi all, new to puppet so excuse my noobiness :)
I've got a puppet type to manage iptables rules (https://github.com/
camptocamp/puppet-iptables) running in my development environment.
The module works great for the most part; rules are calculated and
applied in the right order. The problem is, i
t; do 'rm' instead of 'match'. From your post, I wasn't sure if you had
> [1] http://augeas.net/page/Path_expressions
Perfect, that's just what I was looking for and it works like a charm.
Thanks, Paul.
--
Paul Elliott, UNIX Systems Administrator
Computing Servi
an issue the rm. Am I missing
something obvious here?
--
Paul Elliott, UNIX Systems Administrator
Computing Service, University of York
--
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...@goo
14 matches
Mail list logo