Hi DRC, I did this. And once (before rebooting) it worked. But after reboot it doesn't work anymore. Also the manual start by "sudo systemctl start tvncserver" doesn't work now (it did before rebooting!). "/opt/TurboVNC/bin/vncserver -list" displays no X display and no process id. There is no Xvnc process too. Only the start by "/opt/TurboVNC/bin/vncserver" works as before.
Could you say, what I'm doing wrong? Kind Regards Torsten Am Freitag, 11. Mai 2018 05:20:18 UTC+2 schrieb DRC: > > Edit /etc/sysconfig/tvncservers and specify the TurboVNC Server > instances you want to start, as well as their associated display > numbers, user accounts, and command-line arguments. Then do > > sudo systemctl enable tvncserver > sudo systemctl start tvncserver > > On 5/10/18 4:02 PM, torsten wrote: > > Hi, > > > > I tried to start "/opt/TurboVNC/bin/vncserver" automatically at boot > > time by a systemd unit (OS is Ubuntu 16.04). I used these instructions: > > > > https://wiki.ubuntuusers.de/systemd/Units/ > > https://wiki.ubuntuusers.de/systemd/Service_Units/ > > https://wiki.ubuntuusers.de/systemd/systemctl/ > > > > This is the content of my service unit file: > > > > [Unit] > > Description=TurboVNC-Server > > > > [Service] > > Type=simple > > User=torsten > > Group=users > > WorkingDirectory=~ > > ExecStart=/opt/TurboVNC/bin/vncserver > > > > [Install] > > WantedBy=multi-user.target > > > > When I start "/opt/TurboVNC/bin/vncserver" manually, > > "/opt/TurboVNC/bin/vncserver -list" writes this: > > > > TurboVNC server sessions: > > > > X DISPLAY # PROCESS ID > > :1 14184 > > > > The displayed process id represents the Xvnc process created by > > vncserver, which is the X server used to display the TurboVNC session. > > > > When I kill this server using "/opt/TurboVNC/bin/vncserver -kill :1" and > > start the above service unit using systemctl, > > "/opt/TurboVNC/bin/vncserver -list" writes the same (only the prosess id > > differs), but a process with the new process id doesn't exist (and the > > TurboVNC Viewer fails to connect). I compared the log files written by > > both vncserver calls. They are completely identical (only the time > > stamps differ). So where is the Xvnc process gone when started through > > systemd? Is there a way to get more log file content, that could tell > > me, why Xvnc won't run? If needed I can give some more detailed infos. > > > > Kind Regards > > Torsten > -- 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/75c26c8e-1a6b-4913-959b-1b6943f74d7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
