[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: global configuration patch (ITS#3353)

ozone@symas.com wrote:

>Full_Name: ozone
>Version: HEAD
>OS: Linux
>URL: ftp://ftp.openldap.org/incoming/ozone-0933004.patch
>Submission from: (NULL) (
>this patch migrates all global configuration variables (*except
>ldap_syslog/ldap_syslog_level) into a single struct, which is currently
>referenced by frontendDB->be_private.
>ldap_syslog is used elsewhere; the impact of migrating it isn't clear.
As I guideline I would favour moving all the modifications to back-config,
leaving in back-monitor only the presentation of the current status.  I'd be
in favour of removing the overall update capabilities from back-monitor.
This might lead to duplicates, because changes to back-config, to occur via
protocol, will require to present data much the same as in back-monitor.
In this sense, it may be appropriate to remove some features from 
if they're more pertinent to back-config.

Ata present, the only update-capable data in back-monitor should be the log
level and the readonly/allowed operation stuff in the database entries.


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497