In the LOG library lga this is checked and returned as an INVALID_PARAMETER. The server side allows this for the fixed streams. Should be just a matter of removing the check in the library.
--- old+++ new@@ -1 +1 @@-In the LOG library lga this is checked and returned as an INVALID_PARAMETER+In the LOG library lga this is checked and returned as an INVALID_PARAMETER. The server side allows this for the fixed streams. Should be just a matter of removing the check in the library.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Added the following note in section 2.2.3, compliance report:
Note: The OpenSAF LOG service allows writing zero sized log records. A call to saLogStreamOpen_2() with the attribute SaLogFileCreateAttributesT_2.maxLogRecordSize set to 0 will succeed.
Updated section 3.2.1 saflogger, as below:
saflogger -a myApp
Will make one application stream named “myApp” with empty message. i.e. zero sized log record.
changeset: 102:522d968ac27d
branch: opensaf-4.4.x
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 19:24:35 2014 -0400
summary: log: added note for supporting zero sized log records [#857]
changeset: 103:8b6ab33b700f
branch: opensaf-4.3.x
parent: 94:df34e5be0f19
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 19:53:32 2014 -0400
summary: log: added note for supporting zero sized log records [#857]
changeset: 104:09ba3a2ec82c
tag: tip
parent: 92:1d225bfa1e31
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 19:55:49 2014 -0400
summary: log: added note for supporting zero sized log records [#857]
Diff:
Just tested a patch, it does works the same way as standard streams for zero sized record.
This patch is working.
Fixed in the following changesets.
[staging:b7c820]
[staging:df71c6]
[staging:7a195e]
changeset: 5185:b7c820c3307f
branch: opensaf-4.3.x
parent: 5182:5d2cd5fe07c6
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 18:45:20 2014 -0400
summary: log: allow zero sized log records for app streams [#857]
changeset: 5186:df71c692fec6
branch: opensaf-4.4.x
parent: 5183:f85e23a54a53
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 18:45:20 2014 -0400
summary: log: allow zero sized log records for app streams [#857]
changeset: 5187:7a195e2c63c9
tag: tip
parent: 5184:60d4e2f0455f
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 18:45:20 2014 -0400
summary: log: allow zero sized log records for app streams [#857]
Related
Tickets:
#857Commit: [7a195e]
Commit: [b7c820]
Commit: [df71c6]
Updated documentation in the following changeset:
[staging:522d96]
[staging:8b6ab3]
[staging:09ba3a]
Added the following note in section 2.2.3, compliance report:
Note: The OpenSAF LOG service allows writing zero sized log records. A call to saLogStreamOpen_2() with the attribute SaLogFileCreateAttributesT_2.maxLogRecordSize set to 0 will succeed.
Updated section 3.2.1 saflogger, as below:
Will make one application stream named “myApp” with empty message. i.e. zero sized log record.
changeset: 102:522d968ac27d
branch: opensaf-4.4.x
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 19:24:35 2014 -0400
summary: log: added note for supporting zero sized log records [#857]
changeset: 103:8b6ab33b700f
branch: opensaf-4.3.x
parent: 94:df34e5be0f19
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 19:53:32 2014 -0400
summary: log: added note for supporting zero sized log records [#857]
changeset: 104:09ba3a2ec82c
tag: tip
parent: 92:1d225bfa1e31
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Fri Apr 25 19:55:49 2014 -0400
summary: log: added note for supporting zero sized log records [#857]
Related
Tickets:
#857