On Mon, Apr 18, 2016 at 5:46 PM, James Stallings <[email protected]> wrote: > I believe root cause here was a bunch of old OSSEC processes that were still > holding an older config in memory even after I had cycled the daemons on > several occasions. I no longer see the issue. Has anyone seen this sort of > behavior before? >
It's not common, but it does happen. You can probably find several instances of it on the mailing list. -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
