On 04/09/2015 03:12 PM, Gabriel Filion wrote:
Puppet is really good at managing steady states. Why not have puppet manage
cron entries responsible for starting and stopping the daemon? A custom fact
could be used to return the current on/off state (accurate as of the last
puppet run, or cours
What about setting the state of the service based on clock time ?
It would depend on how often puppet runs.
The cron suggestion would complement this in a nice "belt-and-suspenders"
solution.
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that no
On 09/04/15 02:01 AM, Peter Bukowinski wrote:
> On Apr 9, 2015, at 1:26 AM, Gabriel Filion wrote:
>> A client of mine needs to be able to control which hours during the day
>> a certain daemon is running and which hours it is not.
>>
>> So far I can think of hiera for controlling the on/off period
I had the same issue. /etc/selinux/config to SELINUX=permissive fixed my
issue.
On Tuesday, August 12, 2014 at 8:08:20 PM UTC-5, Patrick Robinson wrote:
>
> I had a similar error getting 405. I found I hadn't set the PassengerRoot
> directory correctly in the puppetmaster vhost config:
>
> Passe
TL;DR: go to http://puppetconf.com to find out details about PuppetConf and
submit a talk proposal, as submissions are now open.
This year PuppetConf is coming back to Portland, Oregon, and I'm really
excited to have the conference come back to the home of Puppet Labs HQ.
It's on Oct 5-9 this ye
Btw. I tried the same thing in Puppet Enterprise by using the "Learning VM"
but the result was the same..
puppet node classify --node-group default --enc-auth-passwd
learningpuppet--enc-auth-user admin --enc-server localhost --enc-port 443
--insecure learning.puppetlabs.vm
Warning: List nodes
Hello everyone,
I had a question I was hoping someone might have an answer to. Essentially
what I'm doing is try to ensure I'm always using a fixed, slightly older
version of phpunit, which I've placed in my module's file resources.
The manifest:
file
{
"/usr/bi
On Wednesday, April 8, 2015 at 4:33:41 PM UTC-5, Scott Jaffa wrote:
>
> John,
>
> Thanks for the detailed reply. While we aren't in agreement on some of
> the finer points, it is moot as you've made it quite clear that the listed
> approaches won't work at a technical level.
> Stepping back, c
I am not necessarily condoning this, but puppet has a "schedule"
metaparameter that can control when a resource may be managed. That
would solve half the problem. You could probably manage it in the
other state using the same trick, but you have to "trick" puppet by
giving the resource another na
