VNC & Suse 8.2 Success with init 5 but Grey window with init 3
Dear Friends, I have very good results when linux box suse 8.2 Pro is running in init 5 mode but i am getting a grey window when its in init 3 mode. The lsof command output shows that vnc server is running but kdm is not listening on port 177. My settings are as listed Below. Can somebody help me in this regard. I would like to access This Linux box irrespective of whether running in mode 5 or 3. Since this box is a database server local administrator often puts it into mode 3 when it slows down in mode 5 Best Regards R. S. Patil ========================================== OS = Suse 8.2 pro Real VNC = VNC vnc-4.0-0b4.i386.rpm Client = WinVNC B4 on Win XP (Dell-Laptop) 1) in /etc/services added lines ---------------------------- vnc640x8 5950/tcp # Small vnc800x8 5951/tcp # Medium vnc1024x8 5952/tcp # Large vnc640x16 5960/tcp # Small vnc800x16 5961/tcp # Medium vnc1024x16 5962/tcp # Large 2) created new file /etc/xinetd.d/VNC ---------------------------------- service vnc640x8 { socket_type = stream protocol = tcp wait = no user = root server = /usr/bin/Xvnc server_args = -inetd -query localhost -once -geometry 640x480 -depth 8 securitytypes=none } ...... similar for rest of services When user was nobody I was getting grey screen with X cursor and no login screen. I changed nobody to root which was mentioned on some web page which I don't remember 3) Edited /etc/X11/xdm/xdm-config ------------------------------ commented "! DisplayManager.requestPort: 0" 4) edited /etc/X11/xdm/Xaccess --------------------------- uncommented * #any host can get a login window 5) edited /etc/opt/kde3/share/config/kdm/kdmrc ------------------------------------------- in the XDMCP section changed enable = true 6) In Yast2-.>System->Sysconfig Editor ----------------------------------- changed DISPLAYMANAGER_REMOTE_ACCESS to yes I think this is only essential setting. changed DISPLAYMANAGER_ROOT_LOGIN_REMOTE = yes this is required if security permits root to be logged in remotely changed DISPLAYMANAGER_STARTS_XSERVER to no to make no gui at console if yes doesn't matter changed KDM_SHUTDOWN to root even if kept unchanged doesn't matter changed KDM_GREETSTRING to "welcome To VNC Server" even if I did this I dont found this greeting at login prompt then saved the changes and rebooted system Aha I can get multiple login windows when tried to connect in VNC viewer even on same port say :52. if display port is added in server_args u get only one connection per port (Ref following) service vnc640x8 { socket_type = stream protocol = tcp wait = no user = root server = /usr/bin/Xvnc server_args = :52 -inetd -query localhost -once -geometry 640x480 -depth 8 securitytypes=none } if Linux is box is running in init 3 I am getting once again grey screen. What shall I do if I want the same results when remote system is running in init 3 mode. outputs of lsof commands in both cases are as follows. Case INIT 5 ==== lsof -I -n -P | grep -v 127.0.0.1 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME portmap 656 bin 3u IPv4 1196 UDP *:111 portmap 656 bin 4u IPv4 1279 TCP *:111 (LISTEN) nmbd 703 root 6u IPv4 1298 UDP *:137 nmbd 703 root 7u IPv4 1299 UDP *:138 nmbd 703 root 8u IPv4 1301 UDP 192.168.10.1:137 nmbd 703 root 9u IPv4 1302 UDP 192.168.10.1:138 ibserver 730 root 0u IPv4 1565 TCP *:3050 (LISTEN) ibserver 780 root 0u IPv4 1565 TCP *:3050 (LISTEN) sshd 831 root 3u IPv6 1622 TCP *:22 (LISTEN) xinetd 1085 root 5u IPv4 3643 TCP *:901 (LISTEN) xinetd 1085 root 8u IPv4 3774 TCP *:9098 (LISTEN) xinetd 1085 root 9u IPv4 3775 TCP *:23 (LISTEN) xinetd 1085 root 10u IPv4 3776 TCP *:5950 (LISTEN) xinetd 1085 root 11u IPv4 3777 TCP *:5951 (LISTEN) xinetd 1085 root 12u IPv4 3778 TCP *:5952 (LISTEN) xinetd 1085 root 13u IPv4 3779 TCP *:5960 (LISTEN) xinetd 1085 root 14u IPv4 3780 TCP *:5961 (LISTEN) xinetd 1085 root 15u IPv4 3781 TCP *:5962 (LISTEN) xinetd 1085 root 16u IPv4 3782 TCP *:21 (LISTEN) smbd 1097 root 9u IPv4 3634 TCP *:139 (LISTEN) kdm 1101 root 6u IPv4 4001 UDP *:177 kdm 1101 root 7u IPv4 4002 TCP *:32769 (LISTEN) X 1121 root 1u IPv4 4012 TCP *:6000 (LISTEN) kdm 1129 root 7u IPv4 4002 TCP *:32769 (LISTEN) kdm_greet 1174 root 7u IPv4 4002 TCP *:32769 (LISTEN) httpd 1226 root 16u IPv4 12042 TCP *:80 (LISTEN) httpd 1227 wwwrun 16u IPv4 12042 TCP *:80 (LISTEN) in.telnet 1514 root 0u IPv4 14299 TCP 192.168.10.1:23->192.168.10.248:1459 (ESTABLISHED) in.telnet 1514 root 1u IPv4 14299 TCP 192.168.10.1:23->192.168.10.248:1459 (ESTABLISHED) in.telnet 1514 root 2u IPv4 14299 TCP 192.168.10.1:23->192.168.10.248:1459 (ESTABLISHED) Case INIT 3 ==== lsof -i -n -P | grep -v 127.0.0.1 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME portmap 656 bin 3u IPv4 1196 UDP *:111 portmap 656 bin 4u IPv4 1279 TCP *:111 (LISTEN) nmbd 703 root 6u IPv4 1298 UDP *:137 nmbd 703 root 7u IPv4 1299 UDP *:138 nmbd 703 root 8u IPv4 1301 UDP 192.168.10.1:137 nmbd 703 root 9u IPv4 1302 UDP 192.168.10.1:138 ibserver 730 root 0u IPv4 1565 TCP *:3050 (LISTEN) ibserver 780 root 0u IPv4 1565 TCP *:3050 (LISTEN) sshd 831 root 3u IPv6 1622 TCP *:22 (LISTEN) xinetd 1085 root 5u IPv4 3643 TCP *:901 (LISTEN) xinetd 1085 root 8u IPv4 3774 TCP *:9098 (LISTEN) xinetd 1085 root 9u IPv4 3775 TCP *:23 (LISTEN) xinetd 1085 root 10u IPv4 3776 TCP *:5950 (LISTEN) xinetd 1085 root 11u IPv4 3777 TCP *:5951 (LISTEN) xinetd 1085 root 12u IPv4 3778 TCP *:5952 (LISTEN) xinetd 1085 root 13u IPv4 3779 TCP *:5960 (LISTEN) xinetd 1085 root 14u IPv4 3780 TCP *:5961 (LISTEN) xinetd 1085 root 15u IPv4 3781 TCP *:5962 (LISTEN) xinetd 1085 root 16u IPv4 3782 TCP *:21 (LISTEN) smbd 1097 root 9u IPv4 3634 TCP *:139 (LISTEN) httpd 1226 root 16u IPv4 12042 TCP *:80 (LISTEN) httpd 1227 wwwrun 16u IPv4 12042 TCP *:80 (LISTEN) in.telnet 1514 root 0u IPv4 14299 TCP 192.168.10.1:23->192.168.10.248:1459 (ESTABLISHED) in.telnet 1514 root 1u IPv4 14299 TCP 192.168.10.1:23->192.168.10.248:1459 (ESTABLISHED) in.telnet 1514 root 2u IPv4 14299 TCP 192.168.10.1:23->192.168.10.248:1459 (ESTABLISHED)
R. S. Patil wrote:
Dear Friends,
I have very good results when linux box suse 8.2 Pro is running in init 5 mode but i am getting a grey window when its in init 3 mode. The lsof command output shows that vnc server is running but kdm is not listening on port 177.
As VNC relies on a running X display you wont be able to do this under runlevel 3 on SuSE - only runlevel 5. See the comments at the top of /etc/inittab. Damian
On Mon, 2004-02-02 at 20:20, Damian O'Hara wrote:
R. S. Patil wrote:
Dear Friends,
I have very good results when linux box suse 8.2 Pro is running in init 5 mode but i am getting a grey window when its in init 3 mode. The lsof command output shows that vnc server is running but kdm is not listening on port 177.
As VNC relies on a running X display you wont be able to do this under runlevel 3 on SuSE - only runlevel 5. See the comments at the top of /etc/inittab.
Damian
But if what you don't want is the graphical interface running on the console you can turn that off. I remember of hand the SuSE 8.2 variable but search yast config parameter for something like "Starts the graphical interface"... when set off init 5 just starts kdm. (then you need to type startx to get a graphical interface on the console)... Jerry
As VNC relies on a running X display you wont be able to do this under runlevel 3 on SuSE - only runlevel 5. See the comments at the top of /etc/inittab.
Damian
But if what you don't want is the graphical interface running on the console you can turn that off.
I remember of hand the SuSE 8.2 variable but search yast config parameter for something like "Starts the graphical interface"... when set off init 5 just starts kdm. (then you need to type startx to get a graphical interface on the console)...
The local admin is switching to init 3 since he wants to conserve memory. by setting Yast2-.>System->Sysconfig Editor DISPLAYMANAGER_STARTS_XSERVER to no will it result in conserving memory or will it require same amount of memory without having GUI at Console. Otherwise I can telnet or ssh Linux box run VNC whenever required to remote control it and when finished stop VNC and end telenet or ssh session. Can u suggest which one is better in point of view of conserving memory resource. Best Regards R. S. Patil
participants (3)
-
Damian O'Hara -
Jerry Westrick -
R. S. Patil