reestablishing gss context on rpc_reconnect
if we receive an rpc_autherr, just recreate a new rpc client as well as the rpc auth structure. as it ties into the recovery and handles that only one thread recovers and reestablishes the rpc auth context. in theory, reestablishing rpc client does not necessitate new rpc auth context. we really need to restablish one only if we get rpc autherr. however, it simplifies the code not to introduce a different synchronization mechanism for rpc auth in addition to the rpc one.
This commit is contained in:
parent
b6beb6f2a9
commit
d6967ea9ef
4 changed files with 94 additions and 38 deletions
|
|
@ -54,6 +54,7 @@ void print_opcode(int level, DWORD opcode);
|
|||
const char* opcode2string(DWORD opcode);
|
||||
const char* nfs_opnum_to_string(int opnum);
|
||||
const char* nfs_error_string(int status);
|
||||
const char* rpc_error_string(int status);
|
||||
void print_condwait_status(int level, int status);
|
||||
void print_sr_status_flags(int level, int flags);
|
||||
void open_log_files();
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue