The main purpose of introducing a configuration object was not to make
configuration changes in runtime except for one specified configuration, the
root directory. However it was discussed to make more configurations runtime
changable in the future and a configuration object makes that possible.
An important possibility when having the configuration in a configuration
object is the possibility to read the configuration and this I think makes it
impossible to use this solution strait off. If environment variables are used
instead of the values in the configuration object there will be a mismatch
between the actual configuration and the configuration that can be read in the
IMM object.
Solution comments:
Solution A:
Handling of environment variables are done as in your patch with the following
addition.
The IMM object is changed to reflect the actual value. This means that all
attributes that can be replaced by environment variables has to be runtime
changable and if an environment variable is used the log service has to use the
IMM Om interface to change the corresponding IMM attribute.
All replacements should be logged in the system log.
This may seems a bit strange for the user. There may be conflicts between for
example old environment variables and new configuration in definition of
configuration object.
Solution B:
For each configuration, check if there is an environment variable. If so don't
change the configuration or the configuration object but log a warning or
possibly an error in the system log.
Make some more configuration runtime changable e.g. the mailbox limits.
NOTE:
Not all configuration is not possible to change in runtime at least not
"logFileSysConfig"
---
** [tickets:#841] LOG: Wrong default logStreamAppHighLimit (1)**
**Status:** fixed
**Milestone:** 4.5.FC
**Created:** Wed Apr 09, 2014 07:07 AM UTC by Hans Feldt
**Last Updated:** Thu Apr 17, 2014 04:18 PM UTC
**Owner:** elunlen
The value is 1 causing writes to be discarded with no buffering.
This was introduced by:
changeset: 4758:2e40297612ec
user: Lennart Lund <[email protected]>
date: Fri Dec 20 13:14:09 2013 +0100
summary: logsv: Handle log files on both active and standby [#152]
Previously the limits were unlimited, this one should be reverted back to 0
(unlimited).
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
