Michal Vasko

> Then I killed my process and started again hoping lock could recover, but it never recovered. That is strange, what *sysrepo* version are you using? > Ideally, there should...

The event originator can send any additional data if it wants, including some identification information. Look at `sr_session_set_orig_name()` and `sr_session_push_orig_data()`. In the callback you read the data using `sr_session_get_orig_name()` and...

Right, I have somehow missed you are talking about NETCONF sessions, `netopeer2-server` uses the functions I mentioned to send session ID and user name of the RPC originator. More in...

I do not understand what that has to do with anything. I have referenced the README because what is written there is correct.

@biswajit84 Sysrepo sessions have their own SID, which is in no way related to NETCONF SID. But the README I referenced tells you how to get NETCONF SID in the...

This is a very special use-case even thought it may not seem that way. But I managed to make it work without too much trouble, so it should be fixed...

I cannot reproduce the issue. It seems you have some broken state after previous crash, maybe caused by the update. Try running `make sr_clean` and then run `sysrepo-plugind` again.

Could you please specify what exactly is wrong in the output? There is a lot of data and I have probably missed it because it seems correct to me.

You did not have to include the code of the plugins, you have attached it before and I have compiled and tested it. The crash is a silly mistake of...

Okay, so on a repeated run I reproduced some issues that were caused by you not closing the `connection` you create in the plugins. But, it should work even then...