If it's not accessible via the API, you can alway "eval" the config file
(though eval is evil) and you would be able to access the @plugins array.
But there must be a better (and safer way of doing it) - something like
evaling it in a namespace so that you don't override your variables.
On Wed, Mar 6, 2013 at 4:27 PM, Rick Hofstede <r.j.hofst...@utwente.nl>wrote:
> Dear all,
>
> According to the Plugin Writers Guide we can access the variables in
> nfsen.conf from a backend plugin as follows:
>
> my $netflow_sources = "$NfConf::PROFILEDATADIR/$profilepath/$all_sources";
>
> Although this works for most settings, it does not for all types. Does
> anyone of you happen to know how you can access the '@plugins' array?
>
> Kind regards,
>
> --
> Rick Hofstede
> University of Twente, The Netherlands
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Nfsen-discuss mailing list
> Nfsen-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Nfsen-discuss mailing list
Nfsen-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
