Issue #2910 has been updated by Markus Roberts.
Status changed from Accepted to Needs design decision
So I'm now thinking that this is "correct" behaviour and the documentation is
wrong. To explain:
* Peter confirmed that there were matching files by running:
<pre>
find /tmp -maxdepth 1 -name 'jna*.tmp' -atime +7 -print
</pre>
* If we use the corresponding tidy, it works fine:
<pre>
tidy { tidy_tmp:
path => "/tmp/",
recurse => 1,
matches => [ "jna*.tmp" ],
age => "7d",
backup => false
}
</pre>
* What *doesn't* work is omitting the recurse, or explicitly setting it to zero
or false (as shown in the example), all of which are the equivalent of setting
-maxdepth to 0 on the find--and give the results you would (or should) expect.
So I'd say tidy is working correctly in the "recurse => false" case (it is
looking at the specified path, and noting else--this would be what you would
want if you were trying to manage a specific file) but the example given for
tidy is wrong.
However, this leaves open the case of the default value for recurse. Should it
perhaps be 1 (only look at direct children of the stated path) or true (look at
all children)? Or should it be required, so that no one can say they were led
astray by an unstated assumption?
----------------------------------------
Bug #2910: tidy failing to remove any matching files
http://projects.puppetlabs.com/issues/2910
Author: Peter Couvares
Status: Needs design decision
Priority: High
Assigned to: James Turnbull
Category: tidy
Target version: 0.25.5
Affected version: 0.25.4
Keywords:
Branch:
I'm somehow unable to get tidy to work _at all_ -- here is what I'm specifying,
right inside a node definition in nodes.pp:
<pre>
tidy { tidy_tmp:
path => "/tmp/",
age => "7d",
backup => false,
matches => [ "jna*.tmp" ],
}
</pre>
The rest of my node definition, and everything else in nodes.pp more generally,
works fine -- but matching files are not being tidied.
I can confirm many matching files on the client host in question with:
<pre>
find /tmp -maxdepth 1 -name 'jna*.tmp' -atime +7 -print
</pre>
I've tried the following in turn, with no luck:
* removing the matches attribute altogether,
* removing the age attribute altogether,
* replacing the matches list with a simple string,
* removing the explicit path attribute and using "/tmp" as the name,
* and setting the type attribute to "mtime" instead of the default atime.
I'm out of ideas, no one on IRC had any other ideas, and so I now suspect a bug.
If I'm doing something foolish, however, I'd be grateful to know. Thanks.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" 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-bugs?hl=en.
