Hello all,
I have been at this for 4 days now and do not seem to find a correct solution.
I need x11vnc to load at the time of the KDE4 login prompt.
I do not want to use the Yast auto login.
x11vnc works just fine if it is manually launched from my user account terminal:
Again I am currently connected to my openSUSE 11.2 (running x11vnc server) from Windows XP machine running realVNC client. (Having to manually launch the x11vnc server of course.) It is working great but If I have to reboot or power is lost I would not be able to reconnect once the openSUSE 11.2 box is back up.
… well … I think you have other options … you could use an ssh client on MS-Windows to restart x11vnc … for example PuTTY: PuTTY: a free telnet/ssh client
Have you ever used YaST? It is the central configuration tool for openSUSE.
When you use YaST > Network Services > Networkservices (xinetd) and you scroll down the list you will find even three vnc services ready for use (that is if you have installed VNC from the OSS repo).
Yes I made sure that VNC was installed at the beginning of this. In the YAST path you provided the 1st VNC service has always been checked but cannot be connected to. I have installed tightvnc hoping to get a result but no joy. Found x11vnc has been in development for some time and works very well but can only be launched manually on this box. I had a suse box at version 10.1 years back and never had this issue of not being able to have a VNC server running ALL THE TIME so i could connect to the CURRENT session logged in running X. I have read through these forums and other distro forums and it seems others can get this to work but not the distro and config I have chosen.
Maybe I have my terminology wrong but if I have tightVNC server running as a service, on a Win32 machine, I can VNC into it if it has been rebooted and at a login screen or connect to the current profile that is logged into it is sitting at the desktop. This not possible in openSuSe any longer?
Sure I could SSH into it, start x11vnc, then vnc into it but a solution it is not.
Thanks for the suggestions but I am still looking.
It does address your inaccurate statement that if there is a PC reboot you would not be able to reestablish a connection.
I think/hope that is clear to you now that YES, even with a reboot, you can survive, albeit you have to login and restart x11vnc.
Now that we have that inappropriate fear out of the way, lets get back to your original question.
Why not write a short script that launches x11vnc, and have that run by your desktop (or if desktop login not assured by the boot process) every boot ?
no my desktop/profile never logged in all the time when auto log in with yast was used. Now I have the server as I want it this is the last thing to get working. Auto log in was used at the beginning for testing but is not wanted at all any longer.
So can a script be run as root so the x11vnc will be running in the back ground before anyone logs in after a reboot?
This is what I wanted to accomplish: Taken from x11vnc: a VNC server for real X displays
I just have not been able to figure it out for openSUSE 11.2 running KDE 4.3
Continuously: Have x11vnc reattach each time the X server is restarted (i.e. after each logout and reboot):
To make x11vnc always attached to the X server including the login screen you will need to add a command to a display manager startup script.
Please consider the security implications of this! The VNC display for the X session always accessible (but hopefully password protected.) Add -localhost if you only plan to access via a SSH tunnel.
The name of the display manager startup script file depends on desktop used and seem to be:
although the exact location can be operating system, distribution, and time dependent. See the documentation for your display manager: gdm(1), kdm(1), xdm(1), dtlogin(1) for additional details. There may also be display number specific scripts: e.g. Xsetup_0 vs. Xsetup, you need to watch out for.
I can’t help you with your script … but one thing I did not see mentioned in this thread, is the application ‘nx’.
Nx provides remote X access to a PC running Linux, and the client can be run on a Mac OS/X, MS-Windows PC, and on a Linux PC. Of course the remote server needs to be running nx.
Note The server PC may be running X, but it does NOT HAVE to be running X. I used to keep a couple of home PCs running in run level 3, but when I access them remotely I would run X on them. Its a truely great piece of software: NoMachine NX - Desktop Virtualization and Remote Access Management Software
I use this software on occasion to access a PC in a different continent, and this capability to access the PC with an X session, even when that remote PC is in run level 3 (and no one logged in) is extremely useful. So as to be clear, I get an X desktop of the remote PC, even though that PC is not running X locally (or that PC can be running X locally, it makes no difference).
I know you did NOT ask about nx, but since I can’t help you with your need for an x11vnc script, I would be remiss if I did NOT mention nx.
I have looked at nx and let just leave it as at this
x11vnc is Coke
NX is pepsi
I prefer Coke. 8^)
I will give pepsi, *cough, NX a try again. I had it installed but be darned if I could figure it out quickly but will give it a go.
If I do not like the taste I will have to got get more Coca Cola™ 8^)
But thank you oldcpu for the suggestions. More research has shown I am one of very FEW ppl wanting to get this done and it is not known why when I attach x11vnc to the display-manager start-up script it will not work. Appears to be a dead end and NX or another distro is what these very FEW have done. I will not let my ignorance have me install another distro over this issue. If anything I will learn more things about linux in the process of configuring remote access to my liking even if it is Pepsi (which does not taste that bad)
nx is easy, but the documentation is intimidating.
Once installed on both “remote” and “local PC”, the client has a nice wizard that one runs to setup access to the remote.
I maintain my mother’s PC in Canada from here in Europe and I setup nx remotely on her PC in Canada while I was in Europe. Of course I had ssh working first. I installed nx on her PC using ssh to install it. And I then ran the nx wizard on my PC here in Europe, and was then able to access her PC. Its great. Its essential. It means if her PC is in run level 3, I can still access her desktop via an X GUI.
Why don’t you try the XDMCP “mode”?
x11vnc got a GDM greeter login screen and you can login. Or do you want to connect to a running session?
I configured XDMCP mode under openSuSE 11.2 (64) with xinetd.
I’m sure the reboot is not a problem.
Warning! Don’t use the package from SuSE software repository! It is old and doesn’t work with GDM (maybe KDM, XDM). It is an old version: 0.9.8.
Use 0.9.10 from x11vnc page. It isn’t packaged and TEST version but it seems working.
If you need more information, please contact to me.
That’s Great! Not sure why it didnt work.
Installed all packages per NX’s site on server and the client on my windows machine. Ran the wizard, on the windows box, but never could connect. I did make sure port 22 was open and could not find any wizard for the server side. I guess it needs an account setup and the uid and pw it asks for it not that of my openSUSE box?
I just found something is wrong. I have putty on my windows box and tried to connect via SSH (on port 22) and get connection refused. I took the firewall down, even though I have port 22 open and still same issue. The SSH libraries are installed so not sure what is going on just yet. This is why NX would not work.
Hi
That would mean you don’t have the sshd service running, open YaST and
go to the runlevel editor and enable/start the service. Then in the
Firewall settings under allowed services in the drop down box select
the Secure Shell Server and add/ finish. You can then re-enable the
firewall.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.2 (i586) Kernel 2.6.31.12-0.2-desktop
up 2:14, 2 users, load average: 0.09, 0.14, 0.17
ASUS eeePC 1000HE ATOM N280 1.66GHz | GPU Mobile 945GM/GMS/GME
Yep found that info while you were posting but thanks for posting as others may stumble on this thread and get help from it.
I uninstalled the free NX server and Node software and installed the FreeNX from the site I mentioned above since it was not limited to 2 connections. NX is very fluid. I do like it. Thanks all for the help and suggestions. Now I can look at more security via SSH and making the NX client a portable app which should not bee too hard but that is another story.
