I don't know the answer to how long the cache hangs around or how to modify
how long it will use the cache but I know that if you run puppet with the
--test option it forces puppet to ignore the cache which is a lot less
annoying then editing the yaml file. I suppose in the puppet.conf for your
cl
Thank you for replying, Silviu.
I could sovled this issue.
Thank you for your cooperation.
Nobuchika Tanaka
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to
Thank you for replying, Calimero.
I could sovled this issue, because you pointed out following:
> Is the time/date set correctly on the puppet client (and everywhere
> else) ?
I compared puppetd host's time/date with puppetmasterd host's one and
found that puppetd host was wrong.
[Puppetmasted
In my testing, puppet has never caught on to a new config or recipe to
distribute unless I manually delete the node entry from the yaml/nodes
directory. I couldn't find any documentation on how to clear the
cache properly (I stumbled on that method) and I couldn't find any
documentation on how lo
I spent some time getting a test site manifest to work with puppetd -
tvd. Now I want to leave puppetd running on the host so that I can
trigger puppet runs remotely with puppetrun.
However, puppetd won't stay alive.
This is on Fedora 10. I issue
# service puppet start
and everything looks g
