>> I am also very disconcerted about the issues involved in setting up new
>> files. You can never, ever, EVER change the mode of a newly installed
>> file without restarting services on all existing machines. That doesn't
>> make any sense.
On Jun 14, 2012, at 4:18 AM, Felix Frank wrote:
> I don't really understand your scenario. There is a new config file for
> service X. It gets installed from a package, presumably the X package
> itself. How are service restarts immediately after package installation
> problematic?
I am building new systems with a default file which is initialized just once.
It looks like this
file { 'my-app.cfg':
ensure => file,
owner => root,
group => root,
mode => 0644,
replace => false,
notify => Service['my-app'],
}
So when we first change the file the service is notified and restarted. Nice.
Now, a few years down the road, we want to start initializing new systems like
this:
group => myapp,
mode => 0664,
If we set this parameter, it will modify all existing files and restart the
service on all existing hosts. This means, in essence, that I can't use a File
object to do this, I must do it with an Exec to avoid the notify happening.
This is very non-optimal. If File is so limited that we must use Execs instead,
I think we're missing the point of having a native File type.
--
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.
--
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.
