Persistent configuration

[frispete]

Hi Michal,

we have some customers struggling a bit with configuring/using this stuff.

While testing this with SLES15SP2, I noticed, that on one hand, this is pretty easy to setup, if you stick to the doc, on the other hand, one has to redo the config all the time after booting, most probably due to the nature of keeping the Xvnc processes running for persistent sessions. Looking into the source, I can see this app configuring Xvnc and whatnot on the fly, but no way of keeping these settings in some persistent way. So the work flow for persistent sessions is, that the first user logining in, will need to setup the session properly for others to come..

Is that correct?

Speaking of processes, I noticed this:

/usr/bin/Xvnc -log *:syslog:30,TcpSocket:syslog:-1 -inetd -MaxDisconnectionTime=5 -securitytypes=none -displayfd 11 -geometry 1920x1200 -AllowOverride=Desktop,AcceptPointerEvents,SendCutText,AcceptCutText,MaxDisconnectionTime,MaxConnectionTime,MaxIdleTime,QueryConnect,QueryConnectTimeOut,AlwaysShared,NeverShared,DisconnectClients,SecurityTypes,Password,PlainUsers -auth /run/vncmanager/auth/1 -desktop VNC manager -extension MIT-SHM

Does providing AlwaysShared,NeverShared make any sense here?

[michalsrb]

Hi,

It is out of vncmanager's scope to automatically create user sessions on boot. But it could remember the last configuration and maybe even have the option to automatically turn a session permanent right after user creates it thru remote connection. PRs are welcome.

Yes, -AllowOverride=AlwaysShared,NeverShared makes sense. This tells Xvnc that X client (like vncmanager-controller) may modify both of these parameters at runtime. It wouldn't make much sense for it to enable both at the same time, but it can enable each of them individually.