TurboVNC doesn't have a proper systemd unit file, but it retains the init.d startup mechanism from TightVNC as a legacy feature. If your distribution has init.d backward compatibility, then you can use the init.d startup mechanism by editing /etc/sysconfig/tvncservers to specify the X display numbers, user accounts, and (optionally) Xvnc arguments for each TurboVNC session that should be started. Then you can run 'sudo systemctl enable tvncserver' and 'sudo systemctl start tvncserver'.
DRC
--
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 turbovnc-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/turbovnc-users/CAGq1ER%3DaW5yWKJsbNVauFFkM1QXcS9WcuiX3nFA%2B4jt4W_m-rg%40mail.gmail.com.