You could just post process the samahain output to ignore files listed in
$puppet/var/state/state.yaml
John
On 8 June 2011 16:14, Robin Lee Powell wrote:
> Sure, but I don't see any way to tell samhain "these files right
> here have changed; trust the new values". I only see "accept
> everythi
Sure, but I don't see any way to tell samhain "these files right
here have changed; trust the new values". I only see "accept
everything".
-Robin
On Wed, Jun 08, 2011 at 02:11:34AM -0400, vagn scott wrote:
> |Does this help?
>
> dpkg -L PACKAGENAME
> |
>
>
>
> On 06/08/2011 01:44 AM, Robin L
|Does this help?
dpkg -L PACKAGENAME
|
On 06/08/2011 01:44 AM, Robin Lee Powell wrote:
(zombie thread rar!)
Where this comes up for me is when I have packages set to "latest".
There's not really any way, I don't think, to integrate samhain into
this process (that is, to say "I just insta
(zombie thread rar!)
Where this comes up for me is when I have packages set to "latest".
There's not really any way, I don't think, to integrate samhain into
this process (that is, to say "I just installed this package with
apt, so update those files").
which is pretty unfortunate, really; th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vince,
If you really want to do this, I would do the first scenario you
describe with a few key points.
1) Let puppet run
2) Have an exec in puppet that runs a job in the background that does
the following:
- Waits until all puppet instances have f
We just starting using samhain on our servers.
Since updates to our puppet manifests tend to change files on the
system that samhain monitors, I'm looking for a good way to
reinitialize the samhain database whenever puppet changes something on
the system to reduce notifications that samhain produc