Can someone tell me where I can find documentation (man pages??) on the xorg-x11-Xvnc servers that are supplied by default within the xinet daemons? Google searches and YaST is turning up nada so I wonder if I am searching for the wrong thing.... Marc... -- Marc Chamberlin www.marcchamberlin.com A man said unto the universe - "Sir I Exist!" "However" replied the universe "I do not see where that creates in me a sense of an obligation" S Crane.
On 07/01/2010 01:00 PM, Marc Chamberlin wrote:
Can someone tell me where I can find documentation (man pages??) on the xorg-x11-Xvnc servers that are supplied by default within the xinet daemons? Google searches and YaST is turning up nada so I wonder if I am searching for the wrong thing....
Marc...
Marc, I'm not sure there is a lot to be found. I'm sure you know this, but sinetd is fairly simple and straight forward. You start/stop xinetd just like any other daemon and xinetd reads the individual service config files in /etc/xinetd.d/. Look in the file for the service you are interested in like say 'tftp', etc.. This will tell you what services are by default available to be run under xinetd. Here is what I have according to chkconfig --list: xinetd based services: chargen: off chargen-udp: off cups-lpd: off cvs: off daytime: off daytime-udp: off discard: off discard-udp: off echo: off echo-udp: off netstat: off nrpe: off nsca: off rsync: off sane-port: off servers: off services: off svnserve: off swat: off systat: off tftp: on time: off time-udp: off vnc: off To enable or disable the xinetd services, just modify the config file for the service you need (vnc?) For example let's look at tftp: -rw-r--r-- 1 root root 2317 2009-12-19 08:58 vnc.rpmsave 14:57 alchemy:/etc/xinetd.d> cat tftp # default: off # description: tftp service is provided primarily for booting or when a \ # router need an upgrade. Most sites run this only on machines acting as # "boot servers". service tftp { socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -s /tftpboot disable = yes To enable the service, just 'undisable' the service by changing 'disable = yes' to 'disable = no' or turn the service on with 'chkconfig tftp on' and then restart xinet.d with 'rcxinetd restart'. (as root of course). You can confirm it is running with 'chkconfig --list' and then look under the xinetd listing. That's about it. You can turn the service off by making disable = yes or with 'chkconfig tftp off' and restarting xinetd. You can always use yast to do this as well, but it is just as easy from the command line. Good luck. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 7/1/2010 1:16 PM, David C. Rankin wrote:
On 07/01/2010 01:00 PM, Marc Chamberlin wrote:
Can someone tell me where I can find documentation (man pages??) on the xorg-x11-Xvnc servers that are supplied by default within the xinet daemons? Google searches and YaST is turning up nada so I wonder if I am searching for the wrong thing....
Marc...
Marc,
I'm not sure there is a lot to be found. I'm sure you know this, but sinetd is fairly simple and straight forward. You start/stop xinetd just like any other daemon and xinetd reads the individual service config files in /etc/xinetd.d/. Look in the file for the service you are interested in like say 'tftp', etc.. This will tell you what services are by default available to be run under xinetd. Here is what I have according to chkconfig --list:
xinetd based services: chargen: off chargen-udp: off cups-lpd: off cvs: off daytime: off daytime-udp: off discard: off discard-udp: off echo: off echo-udp: off netstat: off nrpe: off nsca: off rsync: off sane-port: off servers: off services: off svnserve: off swat: off systat: off tftp: on time: off time-udp: off vnc: off
To enable or disable the xinetd services, just modify the config file for the service you need (vnc?) For example let's look at tftp:
-rw-r--r-- 1 root root 2317 2009-12-19 08:58 vnc.rpmsave 14:57 alchemy:/etc/xinetd.d> cat tftp # default: off # description: tftp service is provided primarily for booting or when a \ # router need an upgrade. Most sites run this only on machines acting as # "boot servers". service tftp { socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -s /tftpboot disable = yes
To enable the service, just 'undisable' the service by changing 'disable = yes' to 'disable = no' or turn the service on with 'chkconfig tftp on' and then restart xinet.d with 'rcxinetd restart'. (as root of course). You can confirm it is running with 'chkconfig --list' and then look under the xinetd listing. That's about it. You can turn the service off by making disable = yes or with 'chkconfig tftp off' and restarting xinetd.
You can always use yast to do this as well, but it is just as easy from the command line. Good luck.
Thanks David, yep I am headed down the path you pointed out.... I was actually looking for documentation on Xvnc which is the Xorg server that comes pre-configured for the xinetd services for the SuSE distros. There are 3 preconfigured vnc servers which are "SUPPOSED" to give one a KDM login window, but for all the 11.x versions of SuSE I have never been able to get them to work. (Google shows me that I am not alone) So I was poking into them and could not find any documentation on Xvnc, other than doing a "Xvnc --help" to get the abbreviated parameter descriptions. In the meantime, I have been using x11vnc instead. (KRDC and Krfb don't work for me either, sigh... This whole VNC world is kinda a mess on SuSE, IMHO!) But today I finally got fed up and tired of using ssh (or explaining how to use ssh to others) to start a remote x11vnc server all the time. So I decided come hell or high water I am going to get a daemon running on all my systems, so I and others around here can use VNC easier. So I have now configured a new xinetd service to work with x11vnc instead of Xvnc. Others might be interested in doing what I have done also, so I will include the necessary info below. This won't give a new login/desktop like the Xvnc services are configured to do, instead this will connect the client VNC to the active desktop on the remote system, but for me that is actually more ideal anywise... This approach also requires one to set up a vnc password file for protection, since the VNC service will be running all the time and we will want to keep the nasty critters out... (Would be really really nice if x11vnc could work with PAM and use that authentication service instead, just a thought....) So for the details.... To set up a x11vnc service, be sure to have the x11vnc modules from the SuSE repository installed on your system. Be sure port 5900 (or whatever port you choose) is open in your SuSEFirewall2. In /etc/xinitd.d create a file called x11vncservice and put the following in it - service x11vncservice { socket_type = stream protocol = tcp wait = no user = root server = /usr/bin/x11vnc server_args = -inetd -rfbauth /etc/vncpasswd -o /var/log/x11vnc.log -find -env FD_XDM=1 port = 5900 type = UNLISTED } Next create the vncpasswd file - cd /etc x11vnc -storepasswd 'yourfavoritepassword' vncpasswd and restart the xinitd services - rcxinetd restart VOILA! A vnc service that actually works on port 5900! SuSE 11.2 x86_64 Marc..
On 07/01/2010 06:00 PM, Marc Chamberlin wrote:
Next create the vncpasswd file -
cd /etc x11vnc -storepasswd 'yourfavoritepassword' vncpasswd
and restart the xinitd services -
rcxinetd restart
VOILA! A vnc service that actually works on port 5900! SuSE 11.2 x86_64
Marc..
Now that's cool! I've poked around a bit and I've tried different vnc solutions, and I agree the competing vnc methods are a mess. That why have always come back to using tightvnc for myself personally. I don't have to worry about setting it up for others. If I want a graphics session, I just start the vncserver on the remote host via ssh, do my thing, and then kill/reset the session the same way. I don't know why, but suse defaults to NOT resetting the vnc session once you terminate it, so I just use a one-liner that kills and restarts the service. From the client, I use the same 'vncviewer' client and it has worked fine. There is both the linux and windows clients, so that is usually convenient. For tunneling into windows boxes, I just stick with rdesktop. Something like: rdesktop killerz.3111skyline.com -u david -g 1280x800 -E -x l & -- or if across the internet -- rdesktop -u david -g 1024x768 -x b -z rbpllc.com always does the trick. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-07-01 at 16:00 -0700, Marc Chamberlin wrote:
VOILA! A vnc service that actually works on port 5900! SuSE 11.2 x86_64
How are you connecting to this from a client? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 7/1/2010 11:32 PM, Roger Oberholtzer wrote:
On Thu, 2010-07-01 at 16:00 -0700, Marc Chamberlin wrote:
VOILA! A vnc service that actually works on port 5900! SuSE 11.2 x86_64
How are you connecting to this from a client?
I have been using vncviewer from Linux clients, and RealVNC viewer from Windoz clients. KRDC will not let me type in a password for some odd reason so I cannot use it when I have the server set up to require authorization, but it might work if no password authorization is used.... Marc..
On Fri, 2010-07-02 at 00:29 -0700, Marc Chamberlin wrote:
On 7/1/2010 11:32 PM, Roger Oberholtzer wrote:
On Thu, 2010-07-01 at 16:00 -0700, Marc Chamberlin wrote:
VOILA! A vnc service that actually works on port 5900! SuSE 11.2 x86_64
How are you connecting to this from a client?
I have been using vncviewer from Linux clients, and RealVNC viewer from Windoz clients. KRDC will not let me type in a password for some odd reason so I cannot use it when I have the server set up to require authorization, but it might work if no password authorization is used....
I use a password file with vncviwer. I was mainly curious if there was some great client I have missed. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/02/2010 02:29 AM, Marc Chamberlin wrote:
I have been using vncviewer from Linux clients, and RealVNC viewer from Windoz clients. KRDC will not let me type in a password for some odd reason so I cannot use it when I have the server set up to require authorization, but it might work if no password authorization is used....
Marc..
Marc, Nonsense. I use a password with vncserver/vncviewer on a daily basis. When you start your first session on the server, starting 'vncserver -geometry XxY -depth 16 :1' you are prompted for a session password that the client will have to use to connect. On every subsequent server start, the server will default to that password. If you set it up without a password, then you can delete the ~/.vnc/passwd file and set it again. Then when you connect from the client you will always be prompted for a password. HTH.. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 7/2/2010 2:01 AM, David C. Rankin wrote:
On 07/02/2010 02:29 AM, Marc Chamberlin wrote:
I have been using vncviewer from Linux clients, and RealVNC viewer from Windoz clients. KRDC will not let me type in a password for some odd reason so I cannot use it when I have the server set up to require authorization, but it might work if no password authorization is used....
Marc..
Marc,
Nonsense. I use a password with vncserver/vncviewer on a daily basis. When you start your first session on the server, starting 'vncserver -geometry XxY -depth 16 :1' you are prompted for a session password that the client will have to use to connect. On every subsequent server start, the server will default to that password. If you set it up without a password, then you can delete the ~/.vnc/passwd file and set it again. Then when you connect from the client you will always be prompted for a password. HTH..
David - No no, I wasn't referring to vnccserver or vncviewer at all... Sorry if I was confusing! I was talking explicitly about using KRDC (it is a vnc client and part of KDE's stuff I believe) as the client only. I cannot get KRDC to let me type in a password, even though it will bring up a password prompt window when it connects to a vnc server that requires one. My suggestion was only to say that if one wants to use KRDC as their client, then it might work if it is connecting to some sort of vnc server that does not require password authorization.... Vncviewer works fine for me, when I connect to any working password protected vnc server, such as x11vnc or RealVNC, as I am using and vncserver as you are using.. I don't consider Xvnc or Krfb (KDE's vnc server) as working vnc servers at the moment, both have been broken for years now and I am giving up hope that they will ever be fixed.... same applies to KRDC. IMHO openSuSE ought to drop these from their default releases until they are fixed, as it will really confuse users and newbies in particular, and cause a lot of aggravation. Using x11vnc (or perhaps vncserver or tightVNC) is an alternative approach that could be picked up and used as a replacement preconfigured xinetd daemon service... But x11vnc needs to be configured if possible, or redesigned to use PAM so that users/administrators don't have to do their own password configuration. (dunno about tightVNC or vncserver, and whether they can even be configured to run as an xinetd daemon) Then the x11vnc service (or perhaps tightVNC, vncserver) could just use the default system authorization services instead... I might poke at both of these issues further, if I have some spare time... Marc... -- Marc Chamberlin www.marcchamberlin.com A man said unto the universe - "Sir I Exist!" "However" replied the universe "I do not see where that creates in me a sense of an obligation" S Crane.
participants (3)
-
David C. Rankin -
Marc Chamberlin -
Roger Oberholtzer