Maciej, Check out export/collect and storeconfigs, as one option.
A simpler way is to generate the cookie once, copy it to the puppetmaster, and distribute it. --Paul On Sat, Nov 15, 2008 at 2:13 PM, Maciej Bliziński <[EMAIL PROTECTED]> wrote: > > Hello puppet-users, > > I'm fairly new to puppet; I've just started to manage few machines at > home with it. I have a question regarding possible ways of handling > pulseaudio cookie distribution. > > My current setup looks like this: > > pulse-server ------(tcp)------ pulse-client-1, pulse-client-2, pulse- > client-3, ... > > There is an authentication mechanism between pulseaudio clients and > the server. Upon startup, server generates a file called pulse-cookie > and places it in /var/run/pulse/.pulse-cookie. Once the file is > created, I go and copy this file over to all the client machines and > put it into /etc/pulse-cookie; pulse client applications read this > file and use it for authentication. > > pulse-client-1 $ sudo scp [EMAIL PROTECTED]:/var/run/.pulse-cookie / > etc/pulse-cookie > Password: > > ...I repeat the procedure on each pulse client. > > I want to automate cookie distribution using puppet. The problem is > that the cookie doesn't originate on puppetmaster, it's being created > on one of puppet clients (pulse-server is a puppet client). > > How would you solve pulse cookie file distribution? > > Maciej > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
