Hi
> Creating the cookie itself perhaps wouldn't be that difficult, but
> after creating and placing it, pulseaudio server would need to be
> restarted. But restarting pulseaudio server is something I'd like to
> happen as seldom as possible, because after such restart all
> connections to it are lost, and clients usually don't reestablish them
> automatically. For instance, flashplayer will just stop playing sound
> until you restart the browser. To sum up the scenario would be:
> generate cookie, place it on the pulseaudio server and then restart
> pulseaudio daemon. But don't restart it if the cookie was already
> there.
The following definition
file{'/path/to/cookie':
source => "puppet:///path/on/server/to/cookie",
[...],
notify => Service['pulseaudio-server'],
}
service{'pulseaudio-server':
[...]
}
will only restart the pulseaudio-server if the content of the file is
changed (which includes created). this is the idea of how this stuff on
puppet should work.
or why do you fear the pulseaudio-server to be restarted more often?
cheers pete
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
