Funny. I was nearly about to give up hope and then that very thought
occurred to me a bit after posting my last message. When I had
initially read the docs, I kind of got the impression that was meant
more for debugging only. As it turns out, it looks to be absolutely
perfect for the task. I have one puppet exec that basically looks
like this:
exec { "offline-files":
command => "rsync -a masterhost:/mastershare/ /offlinefiles;
true"
}
Of course, the host is preloaded with SSH keys to allow rsync to work
w/o any passphrase. This brings across all my manifests, classes, and
other support files to an area on CompactFlash so it becomes non-
volatile to the client. I had to trick puppet through the use of true
in the command because I want puppet to believe this exec always
succeeds. I'd rather it run with old files than to not run at all.
Anyway, thanks for the tip. Had my posts not been delayed due to
moderation of new group members, you'd have saved me lots of grief.
On Dec 12, 1:24 pm, Adam Jacob <a...@hjksolutions.com> wrote:
> Have you thought about side-stepping puppetd/puppetmasterd and just
> writing your manifests to use puppet stand alone?
>
> Adam
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
