For a remote server application, i.e. remote access / control using (real)VNC, the VNC server (for real VNC example = xOvncserver) needs to be started, before a remote connection can be established. So for a new power on condition / reboot without having any other users already logged in, the vnc server needs to be started / already running at the user log-in screen.
In my personal case I am using Real VNC, which starts xOvncserver and Suse 12.1 (64bit) with KDE.
(Thus the standard default option existing Yast2 is not suitable, since xorg-x11-Xunc and tightvnc removed due to compatibility with realVNC)
I have also seen some loose internet information, where for a similar task, it was concluded that since this somewhat complex to implement – a workaround of SSH connection to actually log-in, then server start after user log-in achieved. Putting this to one side / it seems in my mind (at least),that it should not be so difficult to implement a “proper solution” ?.
I have seen various discussed solutions, for similar type start-up applications, by way of various scripts or modifications to config files.
i.e. Links with some notes:
Enabling VNC Server on startup of the X server with SLE 11 (Seems to be a very complex discussion)
HOWTO Configure VNC Server on RHEL5 / CentOS 5 - Consultancy.EdVoncken.NET
Knowledge Base :: Can I start x0vncserver automatically at login time?
Knowledge Base :: Can I start x0vncserver automatically at boot time?
(Noting that it appears that any errors in any of the mentioned approaches, seems likely to lead to a frozen system – I am not really wanting to experiment on this topic).
Not being familiar with any real such solutions, i.e configuration to get server started at log in screen, I would like to request comments / suggestions as to the most recommended / (safe) approach ?. Personally, a single line command calling xOvncserver in a chkconfig or similar would seem to be preferable ?
Thanks for your considerations / time.