Introducing an "empty" OpenSafLogConfig instance was a non backwards compatible
change. How do you plan to adress that?
For convenience I had mentioned it as part of this ticket. Now it is closed but
the problem still remains.
---
** [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:** Fri Apr 11, 2014 11:17 AM 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
