On 2014-09-02 17:36, Henrik Lindberg wrote:
On 2014-09-02 2:53, Amos Shapira wrote:
Hello,
Is there a way to systematically find all modules we have which aren't
used?
Basically, the answer is "no" because it is not possible to statically
analyze puppet code since all inputs are unknown. (Thi
On 2/8/14 8:53 PM, Amos Shapira wrote:
> Hello,
>
> Is there a way to systematically find all modules we have which aren't used?
>
> Two reasons for this question:
>
> 1. We use librarian-puppet to manage "external" modules and would like
> to find which of them can we remove.
> 2. We did
On 2014-09-02 2:53, Amos Shapira wrote:
Hello,
Is there a way to systematically find all modules we have which aren't used?
Basically, the answer is "no" because it is not possible to statically
analyze puppet code since all inputs are unknown. (This because
references to types can be dynamic
I don't think it'll work, even though my servers do check in every 30
minutes:
1. From what I understand, the puppet master caches the manifest and
doesn't re-interpret it unless it changed.
2. I have atime disabled on my servers. It saves tons of disk IO and is
even the default on
I was thinking about this too.
If your servers checkin every 30 minutos you can do:
find /path/to/modules -amin +30
I have not tried it yet,but I suppose it works
Regards,
El 09/02/2014 02:53, "Amos Shapira" escribió:
> Hello,
>
> Is there a way to systematically find all modules we have whic
Hello,
Is there a way to systematically find all modules we have which aren't used?
Two reasons for this question:
1. We use librarian-puppet to manage "external" modules and would like
to find which of them can we remove.
2. We did some major refactoring over the years, in particular
