on my machines, i get in with ssh, and startup vnc by typing either "vk"
(for KDE) or "vg" (for gnome).
first, i disabled:
chkconfig --del vncserver
in my <~/.vnc/xstartup> i have:
(
xrdb $HOME/.Xresources
$wm &
)&>/var/log/xx/vx$DISPLAY
(i never look in the log, but it's there if i want to)
<.bashrc> contains (among other things):
alias xfsstart='[ -f /var/lock/subsys/xfs ]||service xfs start'
alias vk='xfsstart&&wm=startkde vncserver -cc 3 -name kde -geometry 800x600'
alias vk='xfsstart&&wm=$KDEDIR/bin/startkde vncserver -cc 3 -name kde
-geometry 800x600'
alias vg='xfsstart&&wm=gnome-session vncserver -name gnome -geometry
800x600'
alias xg='xfsstart&&xini xg /usr/bin/gnome-session'
alias xk='xfsstart&&xini xk $KDEDIR/bin/startkde'
funct xini(){ (for((x=0;x<=9;x++));do [ -e /tmp/.X$x-lock
]||break;done;rm -f /var/log/xx/$1:$x && xinit $2 -- :$x >
/var/log/xx/$1:$x 2>&1 &);}
if root is calling, it will start xfs if needed.
if a lowly user, xfs must already be running.
and, i modified a line in /etc/rc.sysinit, from:
rm -f /tmp/.X*-lock
to:
action $"Removing X and vnc locks: " rm -rf /tmp/.X*-{lock,unix}
David wrote:
> Thanks for your reply. I don't have a firewall configured for either of my
> machines. (don't need one at the moment) What happen is that I am using a
> laptop and a PC. The PC has sshd running on it. I use my laptop to control
> my PC through a network connection (internal network). So, I ssh into my PC
> from my laptop, tried to start the vncserver by typing "vncserver", before I
> run vncviewer on my laptop to 'see' the PC. The problem now is that there is
> some authorized thingy in the vncserver logs on the PC after I run the
> "vncserver" command through ssh. The vncserver is unable to start properly.
> (or rather KDE is unable to start properly due to:
>
> AUDIT: Fri May 3 02:00:24 2002: 817 Xvnc: client 1 rejected from local host
> Xlib: connection to ":1.0" refused by server
> Xlib: Client is not authorized to connect to Server
> xsetroot: unable to open display ':1'
>
> and many others similar lines with the final lines:
>
> ksmserver: cannot connect to X server :1
> kdeinit: Fatal IO error: client killed
> kdeinit: sending SIGHUP to children.
> kdeinit: sending SIGTERM to children.
> kdeinit: Exit.
>
> So, I would more correctly say that Xvnc started ok, but due to some
> authorization thingy, KDE is unable to connect to Xvnc (since KDE is the
> client here right?). So, how can I go about solving this problem?
>
> I tried to start vncserver from the console of my PC and it works
> wonderfully. But I don't want to do that. I want to do the above.
>
> Thanks,
> David
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
