[FEAT] Env to enable one connection active

[avol-io]

Is this a new feature request?

• I have searched the existing issues

Wanted change

a quick env flag to enable
-new_session_disconnects_existing_exclusive_session: true
-session_type: exclusive

that I think enable the reason for change request

Reason for change

I want only one vnc connection active instance. When I connect from new place the old one will be closed.

Proposed code change

No response

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thelamer]

not 100% on implementation but the flag you are looking for is here:
https://github.com/linuxserver/docker-baseimage-kasmvnc/blob/master/root/etc/s6-overlay/s6-rc.d/svc-kasmvnc/run#L18

Can you do me a favor and modify that in your container (edit the file at the path /etc/s6-overlay/s6-rc.d/svc-kasmvnc/run and remove that line) restart the container and ensure that is the behavior you are looking for ?

[avol-io]

@thelamer i did this test but notting it's changed

[thelamer]

This is not kasmVNC level kclient would need some kind of multi connection detection baked in to kill off the other session.

[avol-io]

@thelamer just to be sure, have you checked this https://www.kasmweb.com/kasmvnc/docs/1.0.0/configuration.html in "user_session" and in particular the session_type? What do you think about it?

[avol-io]

i try to add into /etc/kasmvnc/kasmvnc.yaml

user_session:
  new_session_disconnects_existing_exclusive_session: true
  session_type: exclusive
  concurrent_connections_prompt: false

but not work :-/