Re: name of config_open/config_close

On Tue, 2006-09-05 at 16:46 +0200, Maik Hentsche wrote:
> Hi,
> I started to write a prelude plugin for specter [1], a logging daemon
> for the iptables ulog target. This plugin is included into specter with
> dlopen and links libprelude (0.9.10) with ld -lprelude. Specter has a
> function named config_open and one config_close. Since this names are
> used in libprelude/src/prelude-option.c in function process_cfg_file(),
> the specter functions are used and not the ones defined in
> libprelude/src/config-engine.c. Since these functions seem to be not
> part of the API of the lib, I wonder, if it wasn't better, to use names
> for them, that are less likely to collide with users of the lib (like
> libprelude_config_open). I'm quite sure, this also applies to other
> functions. At the moments, I configured libprelude with
> CFLAGS='-Dconfig_open=libprelude_config_open
> -Dconfig_close=libprelude_config_close', but this is hardly a solution
> but rather a workaround.
> 
> I'd like to hear of your comments,

Hi Maik,

Thanks for reporting this problem. The problem has been fixed in the
Prelude SVN repository: https://trac.prelude-ids.org/changeset/8488

> P.S. When the plugin reached a useable state, will it be desired to post
> it here?

Yes, this would be great!

Regards,

-- 
Yoann Vandoorselaere | Responsable R&D / CTO | PreludeIDS Technologies
Tel: +33 (0)8 70 70 21 58                  Fax: +33(0)4 78 42 21 58
http://www.prelude-ids.com

_______________________________________________
Prelude-devel site list
[email protected]
http://www.prelude-ids.org/mailman/listinfo/prelude-devel