Thanks Lennart.
The attached patch shows what I am going to fix the code regarding your comment
and Mathi's.
Regards, Vu.
>-Original Message-
>From: Lennart Lund [mailto:lennart.l...@ericsson.com]
>Sent: Wednesday, February 24, 2016 3:26 PM
>To: Vu Minh Nguyen; 'Mathivanan Naickan Palan
Hi Vu
In case of an "abandoned" stream the stream object will be removed after a
timeout as I mentioned below but the log file that was the "current log file"
will not be renamed (renamed with a close time stamp). A stream can be
"abandoned" for two reasons:
1. The node with the only client(s)
Hi Mathi,
As Lennart's feedback, in case of getting streamClose, the log agent can remove
the stream from the database, no need to wait till the stream is recovered.
I will update this point. Thanks.
Regards, Vu.
>-Original Message-
>From: Lennart Lund [mailto:lennart.l...@ericsson.com
Hi Vu
Mathi has a point here. It is actually possible to serve stream close also when
headless.
If in state LGA_NO_SERVER the stream can be removed from the agent client
database without sending a message to the (not existing) server.
In IMM there will exist a stream object and if this was the o
Hi Vu,
Ack for patch 2.
B.T.w, What is the idea behind returning try_again for streamclose(), i.e. as
below?
+ if (lga_state == LGA_NO_SERVER) {
+ /* We have no server and cannot write. The client may try again
+*/
+ TRACE("%s No server", __FUNC
osaf/libs/agents/saf/lga/Makefile.am |6 +-
osaf/libs/agents/saf/lga/lga.h | 53 +-
osaf/libs/agents/saf/lga/lga_api.c | 858 --
osaf/libs/agents/saf/lga/lga_mds.c | 46 +-
osaf/libs/agents/saf/lga/lga_state.c | 670 +++
o
