Does setting filetimeout to 0 work? Feels like you should be able to disable re-parsing the config files in Puppet if you want, and if that doesn't work, I'd file a bug.
On Tue, Jun 30, 2009 at 6:22 PM, Greg<[email protected]> wrote: > > The netbackup fix isn't an option unfortunately - causes enough other > grief apparently to be not worth doing. > > I went through the code and looked at what is involved in changing it > to > mtime as an option, and its quite trivial, even for someone like > myself > who doesn't know Ruby well enough yet. My main issue is that I don't > know what depends on that - ie. what its impact is... Maybe I submit > it as a patch and see what the powers that be think of it... > > But on the other hand, its such a minor thing that has no real impact, > so its almost not worth it... > > Greg > > On Jul 1, 12:44 am, Nigel Kersten <[email protected]> wrote: >> On Mon, Jun 29, 2009 at 5:50 PM, Greg<[email protected]> wrote: >> >> > Nigel, >> >> > Actually, its happening 10 mins into backups... And its using >> > Netbackup... >> >> > Looks like I'm stuck with it, unless its possible to get that check to >> > happen on mtime >> > instead of ctime... (Of course then theres the question of which is >> > more useful, etc...) >> > Its not a major issue... The only real issue is that it pollutes the >> > logs a little bit... >> >> http://seer.entsupport.symantec.com/docs/200644.htm >> >> a. At some sites, saving and restoring a file's atime, while leaving >> the file's ctime in its changed state, may present a problem. To cause >> NetBackup to not reset the file's access time, insert the keyword >> DO_NOT_RESET_FILE_ACCESS_TIME in the /usr/openv/netbackup/bp.conf file >> of the client. >> >> so this will mean that your atime is continually changing as files are >> backed up, but as the atime is not reset, the ctime will be left >> alone. >> >> Until I found that I had vague thoughts of a Puppet patch to use a >> checksum instead of ctime for parsed files, but this is the only time >> using the ctime has bothered me. >> >> >> >> >> >> > Thanks, >> >> > Greg >> >> > On Jun 30, 1:50 am, Nigel Kersten <[email protected]> wrote: >> >> On Sun, Jun 28, 2009 at 4:42 PM, Greg<[email protected]> wrote: >> >> >> > Hi all, >> >> >> > I've noticed roughly every 24 hours my puppetmasters will reread the >> >> > puppet.conf even if there is no change to >> >> > the file. Logs look something like this: >> >> >> > Jun 27 18:15:10 puppet-prod puppetmasterd[15161]: [ID 702911 >> >> > daemon.notice] Sat Jun 27 18:09:43 +1000 2009 vs Fri Jun 26 18:06:11 >> >> > +1000 2009 >> >> > Jun 27 18:15:17 puppet-prod puppetmasterd[15200]: [ID 702911 >> >> > daemon.notice] Reparsing /etc/opt/csw/puppet/puppet.conf >> >> >> > Does anyone know if we can influence the frequency of this? I'd like >> >> > to make it less frequent as it re-reads the config file as soon as its >> >> > changed anyway (not that it changes much anyway)... Maybe weekly is >> >> > sufficient... >> >> >> Does this happen to correlated to backup times on these servers? >> >> >> I ran into an issue with NetBackup where by default it restores the >> >> atime of a file after backing it up, which modifies the ctime of the >> >> file, which causes Puppet to think that the file has changed and >> >> reparse it. >> >> >> > thanks, >> >> >> > Greg >> >> >> -- >> >> Nigel Kersten >> >> [email protected] >> >> System Administrator >> >> Google, Inc. >> >> -- >> Nigel Kersten >> [email protected] >> System Administrator >> Google, Inc. > > > -- Nigel Kersten [email protected] System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
