Ok, now I understand what you mean. However, the object does not only contains 
the configuration defined in logsv_objects.xml it also contains default values 
given in the class definition. This makes the content of the configuration 
object looks like this:
The object does not only contains the configuration defined in 
logsv_objects.xml it also contains default values given in the class 
definition, logsv_classes.xml. This makes the content of the configuration 
object looks like this:

# immlist logConfig=1,safApp=safLogService
Name                                               Type         Value(s)
========================================================================
logStreamSystemLowLimit                            SA_UINT32_T  0 (0x0)
logStreamSystemHighLimit                           SA_UINT32_T  0 (0x0)
logStreamAppLowLimit                               SA_UINT32_T  0 (0x0)
logStreamAppHighLimit                              SA_UINT32_T  1(0x258)
logRootDirectory                                   SA_STRING_T  
/repl_opensaf/saflog 
logMaxLogrecsize                                   SA_UINT32_T  1024 (0x400)
logMaxApplicationStreams                           SA_UINT32_T  64 (0x40)
logFileSysConfig                                   SA_UINT32_T  1 (0x1)
logFileIoTimeout                                   SA_UINT32_T  500 (0x1f4)
logConfig                                          SA_STRING_T  logConfig=1 
logAmfHctDefMaxDuration                            SA_TIME_T    180000000000 
(0x29e8d60800, Thu Jan  1 01:03:00 1970)
SaImmAttrImplementerName                           SA_STRING_T  safLogService 
SaImmAttrClassName                                 SA_STRING_T  
OpenSafLogConfig 
SaImmAttrAdminOwnerName                            SA_STRING_T  IMMLOADER

All attributes can be given another value than the value given in the class 
definition by setting a new value in the object (in the logsv_objects.xml file 
or an equivalent used in  system configuration).
A system using the log service should have its own logsv_objects.xml file 
containing a suitable configuration for the log service and that file should be 
used when creating the imm.xml file instead of the default Open SAF file. 
Attributes that does not have to be configured in any other way than 
pre-defined may be omitted.



---

** [tickets:#841] LOG: Wrong default logStreamAppHighLimit (1)**

**Status:** unassigned
**Milestone:** future
**Created:** Wed Apr 09, 2014 07:07 AM UTC by Hans Feldt
**Last Updated:** Thu Apr 10, 2014 11:59 AM UTC
**Owner:** nobody

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.
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to