-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> It does seem fixed in 2.6.1rc3, however 0.25.5 it is still happens.
> Has there been a convergence of opinion on how to roll out 2.6.x?
> Server first then clients? Clients first then the server?
> Everything at once? (that is hard obviously)
alway
Hi Pete,
It does seem fixed in 2.6.1rc3, however 0.25.5 it is still happens. Has there
been a convergence of opinion on how to roll out 2.6.x? Server first then
clients? Clients first then the server? Everything at once? (that is hard
obviously)
Thanks,
derek
On Sep 2, 2010, at 11:51 AM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> So if you make a change in the directory it will correctly refresh
> the services. However the next time puppet runs, it will notice
> there is a mtime difference on the directory and this will also
> trigger a refresh.
>
> notice: //cdh::cdh3/File
Hi,
So for awhile I have been seeing this issue but it hasn't been painful.
However, recently I have been deploying a new module that has made it much more
annoying.
file { cdh3_config:
recurse => true,
ignore => ".svn",
checksum => md5,
