issue : logd is crashing becuse unlocking a mutex twice with out lock
fix :corrected lgs_ftcom_mutexmutex lock and unlock sequence
---
src/log/logd/lgs_filehdl.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/log/logd/lgs_filehdl.cc b/src/log/logd/lgs_filehdl.cc
in
Summary: log: correct mutex lock and unlock sequence in logd [#2452]
Review request for Ticket(s): 2452
Peer Reviewer(s):lennart/vu/canh
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop
Development branch: ticket-2452
Base revision: 41d95e8d68715acacc002d
Hi Lennart,
Thanks for more clarify `the rest of the handling is not affected` given
more clarity, but still I didn't get the advantage of sending
TRYAGAIN instead of TIMEOUT to agent.
Can you please clarify below doubts as well, tagged with [AVM]
On 5/10/2017 4:27 PM, Lennart Lund wrote:
> Hi
Hi Mahesh
When I read your comments I think there may be some misunderstanding of the
problem and of how it is solved so I will try to clarify.
Problem:
If there are many agents sending requests to the log server, requests may come
in faster than the server can handle them meaning that there ma
in the PR doc.
-Nagu
> -Original Message-
> From: Nagendra Kumar
> Sent: 10 May 2017 15:06
> To: Gary Lee; Alex Jones; Anders Widell; nagendra . k @ oracle . com;
> lennart.l...@ericsson.com
> Cc: opensaf-devel@lists.sourceforge.net
> Subject: RE: [PATCH 1/1] doc: update general and AMF r
Hi Gary,
I think it is required to write the steps (with exact commands to add
new class) to perform while upgrading and then after upgrading
enabling/disabling the options and then downgrade (deleting the newer class).
Thanks
-Nagu
> -Original Message-
> From: Gary Lee [mailto:
Hi Canh Van,
Please check my comments as [AVM].
-AVM
On 5/10/2017 12:06 PM, Canh Van Truong wrote:
>
> Hi Mahesh,
>
> Thanks for your update.
>
> Please check my comments.
>
> Regards
>
> Canh
>
> -Original Message-
> From: A V Mahesh [mailto:mahesh.va...@oracle.com]
> Sent: Wednesday, M
