Kumaran,
Xvnc does exactly the samething as you want.
However, this is not the same session as the defualt display :0
of the vnchost machine. It will be a new session,
but persistent across connections.
vamsi
>>> kumaran <[EMAIL PROTECTED]> 06/08/05 10:24 AM >>>
hi,
whenever user gets discon
helps!!!
regards
Vamsi Krishna
>>> "Manjunath M[IS]" <[EMAIL PROTECTED]> 06/03/05 3:12 PM >>>
Hi Vamsi,
We are using VNC to connect to Suse linux server from pc's every time
we try
connecting a lock file is created in suse linus server. Please let us
Alan,
>in the server_args option, when I try to connect via 'vncviewer' with
>the option
> -securitytypes=VncAuth
>included or not there at all, then the vnc password screen pop up and
>request the password. However it always fails. You can see that I tried
>to specify my personal password fi
hmmm..
It needed not be as complex as hacking the vncserver perl script.
vncserver script creates the cookie file and passes it to the Xvnc
server it launches as the auth parameter
Also, you can use vncserver to override this behaviour by passing your
own xauth file.
So if you could say
# vncser
Adding on Robert's suggestion,
>
>> This seems to be required for the shell to start stuff in the :0.0
>> display.
>> At least, when I changed XAUTHORITY to point at ~/.Xauthority, I
found I
> >could then run stuff in :1, but not in :0.
>Presumably your setup is different, but normally Fedora 3 r
Stefan,
Is it that you are seeing an xterm in your VNC session ?
If that is the case, you have to edit your xstartup file in
$HOME/.vnc/xstartup
See the contents of your $HOME/.vnc/xstartup
you will find that a xterm and twm is launched if this is the defualt
file.
You can comment the lines xte
