I've also used facter.d for facts that require longer to run than you want
to wait for a Puppet run.
For example a big find to check all of / for setuid files, then count them.
Run that in a cron then write to facter.d, then grab it with facter.
On Fri, Sep 5, 2014 at 5:04 PM, Khoury Brazil
w
On Thu, Sep 4, 2014 at 9:26 AM, jcbollinger
wrote:
>
>
> As long as you intend to perform the validation inside the fact
> implementation, the fact can keep and use its own cache somewhere on the
> system.
>
> Alternatively, the master stores the most recent set of facts provided by
> each node, a
Admittedly I haven't. I didn't really want to go chasing after something
that has an established practice/pattern or is for some reason a bad idea.
I assumed Facter.value would pull from a cache of some sort, but clearly
that was just a speculative fantasy on my part. If it computes it each time
F
The few times I've had to do things like this (like pulling information
from a physical inventory database to find the rack a host is in, for
monitoring) I've just cached the fact value on disk, usually using some
sort of mtime-based TTL. That being said, I've only done this for facts
that are "opt
On Wednesday, September 3, 2014 11:32:54 AM UTC-5, Khoury wrote:
>
> Sorry for the delay Felix. Here's a specific example of a situation where
> the fact might return what I would consider useless information and I would
> want to revert back to a the value set previously:
>
> On OS X you can h
On 09/03/2014 06:32 PM, Khoury Brazil wrote:
> Sorry for the delay Felix. Here's a specific example of a situation
> where the fact might return what I would consider useless information
> and I would want to revert back to a the value set previously:
>
> On OS X you can have an active user that is
Sorry for the delay Felix. Here's a specific example of a situation where
the fact might return what I would consider useless information and I would
want to revert back to a the value set previously:
On OS X you can have an active user that is at the console and owns
/dev/console. If you want to
On 08/28/2014 11:01 PM, Khoury Brazil wrote:
> I currently have it written to reuse the data using Facter.value() after
> validation but wanted to make sure there wasn't something standardized
> that I missed.
Can you provide an example of that? I don't really see what you did there.
--
You rece
I'm writing some facts for laptops and they're dependent on the
availability of specific services over the network. I'd like to use the
previous data for the fact if the data returned doesn't validate. Is there
an existing pattern I can use for that? I currently have it written to
reuse the data us
