From: Guido S. <gui...@gm...> - 2021-02-23 18:39:36
|
Am 23.02.21 um 17:03 schrieb Simon Ahrens: > Dear all, Hi Simon, > Now I've stumbled upon an issue locking GLs that I hope you can help > me with: Whenever I try to lock one GL, the server seems to lock all > GL but without sending 100 INFO messages about it. Here is what's > happening (locking from session ID 887): [...] > > The server is running srcpd 2.1.3. Can you explain this behaviour? It > seems to be working as I'd expect for GA devices, by the way (lock > one, the others remain unlocked). > Locks are not heavily tested. I don't know if there is any SRCP client which supports this feature. Having just a quick glance at the source code I found regarding the GL devices locks are implemeted on bus level. I have no clue if this is intended or not, but I guess this is an error. Guido |