On Mar 14, 2010, at 18:37 EDT, Luke Kanies wrote: > On Feb 26, 2010, at 12:07 PM, Alan Sparks wrote: > >> I've a tidy resource for /tmp under 0.24.8, which throws errors each run >> due to a socket file created by xfs under /tmp/.font-unix/. It's >> relatively harmless, but it fills the logs with error messages... >> >> /var/log/messages.4:Jan 31 04:01:34 vm03 puppetd[15362]: >> (//Node[vm03]/Tidy::Olderthan[/tmp]/Tidy[/tmp/.font-unix/fs7100]/ensure) >> change from /tmp/.font-unix/fs7100(age)1264176925 to anything failed: >> Cannot tidy files of type socket >> >> Since tidy does not have a parameter for directories or files to ignore, >> and there's no option to specify the types of files to consider, is >> there any way short of hacking the code to eliminate these errors? > > I don't think so. > > I basically threw that failure in there because I wasn't sure what the > behaviour should be for anything other than the standard file types. It'd be > pretty easy to fix tidy to behave appropriately if you can describe how it > should actually behave.
I know for the particular case of /tmp, I would want it to remove any type of file it could encounter. Off hand, I cannot think of a situation where I would be using tidy that I would not want to either be able to filter for a specific file type and only filter that type, or would want to tidy everything. Luke -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
