Because of the opensaf default created "empty" OpenSafLogConfig instance,
configuration via environment variables is deliberately by design skipped. Even
though no configuration of this is included in the OpenSafLogConfig instance.
This is described in the README but is not backwards compatible and has caused
us quite a lot of trouble.
So either
1) opensaf does not create any OpenSafLogConfig instance or
2) if limits are empty in the OpenSafLogConfig instance it should use
environment variables (as before)
I don't see a new ticket for this problem.
---
** [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:** Mon Apr 14, 2014 03:04 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.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
