12-20-2008
Problem with VNC
Hi all,
I have a RHEL 5.0 vnc server. It is running on runlevel 5. When I try to connect with vnc client on Windows machine, it connects with no graphics. A terminal comes look like runlevel 3. When I check the run level on the terminal, it shows 5. I have both desktop (Gnome & KDE) installed on that server. Any suggestion?
Thanks in advance!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone know of a site where I can download a copy (non-evaluation copy and preferably free. ;) nods to Neo's post in UNIX Operating System thread) of VNC for RedHat 8? Thanks in advance. (7 Replies)
Discussion started by: google
7 Replies
2. UNIX for Advanced & Expert Users
i'm starting to think i post too much.
alright a new problem... i'm trying to do the "make World" for Xvnc, and i keep running into the following error:
# make World
Building Release 6.3 of the X Window System.
I hope you checked the configuration parameters in ./config/cf
to see if... (2 Replies)
Discussion started by: xyyz
2 Replies
3. Linux
Hi All,
I really love this forum, i put here many problem and i got the solution.
thanks to all forum guys.
I am putting another problem here actually this problem in my VNC session
to start the VNC session i am running :
#vncserver -geometry 1024x768 -depth 24
New... (0 Replies)
Discussion started by: daya.pandit
0 Replies
4. Windows & DOS: Issues & Discussions
Hi,
Am unable to cut & paste between the VNC windows client and local Windows machine.
In few VNC windows client, i was able to do. (2 Replies)
Discussion started by: param_it
2 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
I have vncserver installed on Sun Solaris 8. The xstartup file looks like:
#!/bin/sh
&& xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
/usr/dt/bin/dtwm &
I have installed VNC on /usr/local/bin. When I try to... (0 Replies)
Discussion started by: naw_deepak
0 Replies
6. Red Hat
Hello all,
I have the folowing problem:
When I connected to a VNC server instance, the screen on the vncserver was frezzed. So, I executed the following commands in order to reestablish the VNC instance:
service vncserver stop
service vncserver start
No problem at this point, but now when... (5 Replies)
Discussion started by: mig28mx
5 Replies
7. UNIX for Dummies Questions & Answers
Hi every one please help to find a way for remote connect to a graphical sco unix Xsession whit tight vnc
i had installed tightvnc on sco unix 5.0.6 and i connect to new session with tight vnc client but i want to connect to started X session and control it
xstartup file
... (0 Replies)
Discussion started by: kaydream
0 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I am having a linux machine and i used to work on this machine either directly or by using vncviewer from my windows machine. So everytime i launch new terminal on my vnc view i need to set DISPLAY. So i added the following code in my .cshrc
if ($?VNCDESKTOP == 1) then
setenv... (1 Reply)
Discussion started by: sarbjit
1 Replies
9. Solaris
hi all
i cant connect to vnc viewer ... when i try it showing follwing error message
write/select : connection aborted (10053)
Do you wish to attempt to reconnect to 1##.2##.###.1# #
help me any one solved before this problem (3 Replies)
Discussion started by: coolboys
3 Replies
10. AIX
Hello,
I install VNC server 5.2.1 on AIX 5.3 and when i try to connect with VNC viewer it get error message : "The connection was refused by the host computer"
Hope u guys can help me
Thanks (3 Replies)
Discussion started by: moudmm
3 Replies
RUNLEVEL(8) runlevel RUNLEVEL(8)
NAME
runlevel - Print previous and current SysV runlevel
SYNOPSIS
runlevel [options...]
OVERVIEW
"Runlevels" are an obsolete way to start and stop groups of services used in SysV init. systemd provides a compatibility layer that maps
runlevels to targets, and associated binaries like runlevel. Nevertheless, only one runlevel can be "active" at a given time, while systemd
can activate multiple targets concurrently, so the mapping to runlevels is confusing and only approximate. Runlevels should not be used in
new code, and are mostly useful as a shorthand way to refer the matching systemd targets in kernel boot parameters.
Table 1. Mapping between runlevels and systemd targets
+---------+-------------------+
|Runlevel | Target |
+---------+-------------------+
|0 | poweroff.target |
+---------+-------------------+
|1 | rescue.target |
+---------+-------------------+
|2, 3, 4 | multi-user.target |
+---------+-------------------+
|5 | graphical.target |
+---------+-------------------+
|6 | reboot.target |
+---------+-------------------+
DESCRIPTION
runlevel prints the previous and current SysV runlevel if they are known.
The two runlevel characters are separated by a single space character. If a runlevel cannot be determined, N is printed instead. If neither
can be determined, the word "unknown" is printed.
Unless overridden in the environment, this will check the utmp database for recent runlevel changes.
OPTIONS
The following option is understood:
--help
Print a short help text and exit.
EXIT STATUS
If one or both runlevels could be determined, 0 is returned, a non-zero failure code otherwise.
ENVIRONMENT
$RUNLEVEL
If $RUNLEVEL is set, runlevel will print this value as current runlevel and ignore utmp.
$PREVLEVEL
If $PREVLEVEL is set, runlevel will print this value as previous runlevel and ignore utmp.
FILES
/run/utmp
The utmp database runlevel reads the previous and current runlevel from.
SEE ALSO
systemd(1), systemd.target(5), systemctl(1)
systemd 237 RUNLEVEL(8)