Do we think OK is an appropriate error code here?
Maybe TIMEOUT?
/Hans

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: den 3 september 2014 13:45
> To: Hans Feldt; Hans Nordebäck; [email protected]
> Cc: [email protected]
> Subject: [PATCH 1 of 1] amfd: respond to shutdown op if lock has been issued 
> before it completes [#1021]
> 
>  osaf/services/saf/amf/amfd/si.cc |  4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> 
> If shutdown op is undergoing, lock can be issued.
> If lock is isued, Amf is not responding to shutdown op.
> Amf should ideally respond to shutdown op immediately after
> it receives lock op. And after lock op completes, then Amf
> should respond to lock op.
> 
> diff --git a/osaf/services/saf/amf/amfd/si.cc 
> b/osaf/services/saf/amf/amfd/si.cc
> --- a/osaf/services/saf/amf/amfd/si.cc
> +++ b/osaf/services/saf/amf/amfd/si.cc
> @@ -881,6 +881,10 @@ static void si_admin_op_cb(SaImmOiHandle
>                               report_admin_op_error(immOiHandle, invocation, 
> SA_AIS_ERR_TRY_AGAIN, NULL,
>                                               "'%s' other semantics...", 
> objectName->value);
>                               goto done;
> +                     } else {
> +                             rc = SA_AIS_OK;
> +                             avd_saImmOiAdminOperationResult(immOiHandle, 
> si->invocation, rc);
> +                             si->invocation = 0;
>                       }
>               }
> 

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to