On Thu, Sep 8, 2011 at 6:12 PM, jplee3 <[email protected]> wrote: > Hi all, > > I was wondering if the "<disabled>no</disabled>" directive under > Active Response is supposed to be a global setting or if it's supposed > to be local to each individual AR. >
That setting is not local to each AR. > The reason is because I set a couple ARs to <disabled>yes</disabled> > to try to prevent them from loading since we don't currently have the > scripts for them (they are in 'development' I suppose you could say). > In doing so, we started noticed that none of the ARs were firing. I > went back into the conf and set <disabled> to "no" and restarted and > everything works again. I noticed the ar.conf file was empty prior to > returning to the disabled no state; after restarting with disabled no, > all the ARs were back in the ar.conf > > > Just wondering if this behavior is intentional or if we're supposed to > be able to set <disabled>no</disabled> per AR. > > It's fine if not - commenting out works too. It would be good to have > this clarified however. > > > TIA
