Michal Vasko

This is simply not going to work. Here is the scenario. Every subscription has its event pipe (for notifying) but you can have 2 subscription for a single structure (sharing...

I have replied in the PR but I would like to add some context. The current design is intentional (but also seemed natural at the time of implementation) because it...

So what exactly are you doing with each NETCONF session? You subscribe to notifications and then periodically send a notification and send a `get`?

Actually, it seems you are not really using *sysrepo* `devel` because according to the stack trace ``` #3 0x00007ffff6b57a76 in __assert_fail () from /lib64/libc.so.6 #4 0x00007ffff6f3c16d in sr_shmsub_multi_listen_write_event (multi_sub_shm=0x7ffff7fba000, valid_subscr_count=4,...

I am telling you are **not** using *sysrepo* `devel` according to the stack trace. There can be several reasons for this, such as you having installed several versions and some...

You need to look at `/usr/local/lib64/libsysrepo.so.7` because it is just a symlink, the target should be `/usr/local/lib64/libsysrepo.so.7.8.0` because that is the current `devel`. You know you are using it if...

Looking at `_3gpp-common-trace.yang` ```yang leaf tjTraceCollectionEntityAddress { when './tjTraceReportingFormat = "FILE_BASED" or ' +'./tjJobType = "LOGGED_MDT_ONLY" or ./tjJobType = "LOGGED_MBSFN_MDT"'; type union { type inet:uri; type inet:ip-address; } mandatory true;...

> Is it possible to handle data for different netconf clients separately in sysrepo provided only one instance of netconf server is running? No, it would go against the principle...

If you really want to have several separate instances of *sysrepo*/*netopeer2* on a single machine, you can achieve it using [environment variables](https://github.com/sysrepo/sysrepo/#used-run-time-enviromental-variables).

More env variables would be useless. The point is to set the variable to a different value for each separate instance.