Why do you need to use xinetd? Can't you just use the existing TurboVNC service?
On 12/25/19 6:39 AM, Stephan von Krawczynski wrote: > Hello all, > > I am on arch linux and tried something quite simple - at least I thought it > was. I wanted to start a vnc service with xinetd which acts persistent. This > should be easy because handling remote vnc logins isn't really that odd. But I > found out that this is quite a problem. Even if stepping down and trying > dynamic sessions (wait=no in xinetd) I still cannot get it working. So I'd > like to ask here if anyone has something like this working and can share > a known-to-work xinet config file for turboVNC. Please don't point to man > pages > (like the one from TigerVNC Xvnc because none of that works, I tested them > all). > Any hints? > -- You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/17249fbf-cc67-d272-4389-8ac89d0c9c12%40virtualgl.org.
