CBee 

Thanks for the help.  I tried using telnet fom a DOS command shell on a
windows machine.  I telneted into the Solaris x86 box and tried running the
script that starts up the vncserver .  The server started up and desktop
looked fine on viewer connection  until I closed the DOS telnet session.
Then the grey screen came back.

When I tried starting the vncserver directly by telnet (rather than by
script) the grey screen was there from the outset.

$ nohup vncserver geometry 1150x950 &

I definitely need a persistent vncserver.  I do not want to do the inetd
thing.

I feel like Im really close to an answer here  its frustrating!

Joel

-----Original Message-----
From: Beerse, Corni [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 19, 2003 8:40 AM
To: 'Joel E. Lieberman, Ph.D.'; Steve Palocz; '[EMAIL PROTECTED] Com'
Subject: RE: Intermittent problem on Solaris x86

> -----Original Message-----
> From: Joel E. Lieberman, Ph.D. [ mailto:[EMAIL PROTECTED]
>
> Yes, please provide any script details that you can.
>
> I think I have discovered something else that may be
> relevant.  As long as I
> don't logout of the Unix session where vncserver was invoked,
> I can come
> back with the viewer (on an external box) and see the CDE desktop
> repeatedly.  Once I logout of the invoking session, however,
> the grey screen
> appears.  The Xvnc process is still running (I can connect
> with viewer) but
> the desktop disappears.  I don't understand X enough to know what this
> means, but I bet it is significant.
If this is the case then I think tooltalk is in the way. It's a problem with
many display-managers, the ones that in the end start the window manager and
accompanying tools).
ON cde, tooltalk is used. Both gnome and kde have a similar construction.
One of the things they do is avoid a double startup in a single login
session. You most likely started vncserver from within a graphical login
session and like to start an other one.
The best thing is to somehow fake or arange an other login to start the new
display manager session in the vncserver session. Some sulutions include:
`rsh localhost vncserver` This starts a vncserver from a fresh login. Nice
part: it can be invoked from an other machine or such. Alternates include
rlogin, rexec, telnet and such.
Run vncserver from an `at`, `batch` or `cron` job. Nice thing here: once the
vncsesion gets killed, you only have to wait for an other session to start.
This is not my prefered way but it gets things going.
The best way, is as on
http://www.sourcecodecorner.com/articles/vnc/linux.asp. This is the intended
(perfect?) way to use the "-once" (here "-inetd" wich includes the same
behavoure) and "-query localhost " as opposed before. Disadvantage here: no
static sessions. However, I see this as an advantage: no stale sessions....

CBee
>
> Joel
>
> -----Original Message-----
> From: Steve Palocz [ mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 18, 2003 3:54 PM
> To: 'Joel E. Lieberman, Ph.D.'; '[EMAIL PROTECTED] Com'
> Subject: RE: Intermittent problem on Solaris x86
>
> I was having this problem also. That is when I started looking at
> invoking Xvnc directly with the options (instead of letting the perl
> wrapper script handle it) (this was originally to turn up debuggin to
> find out what was going on, but still couldn't identify).
>
> I found using the -query localhost, you get the dtlogin and the cde
> desktop, just like on the console. I also use the -once option to kill
> vnc when I click exit on the dtpanel. Then loop the script to start a
> fresh session.
>
> If you would like the command line I use, let me know.
>
> Steve
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [ mailto:[EMAIL PROTECTED] On
> Behalf Of Joel E. Lieberman, Ph.D.
> Sent: Wednesday, June 18, 2003 2:08 PM
> To: [EMAIL PROTECTED] Com
> Subject: Intermittent problem on Solaris x86
>
> Hi Folks -
>
> I am having an intermittent problem with VNC Server on Solaris x86.  I
> run
> the vncserver to start (Xvnc). I have appropriate entries in
> ../.vnc/xstartup to invoke the CDE windows manager.
>
> The problem is that about 80% of the time, The remote vncviewer will
> connect
> to the server and the correct desktop will be displayed, however, at
> other
> times, the "grey screen" will be displayed instead of the CDE desktop.
> Also, sometimes the first couple of viewer connections will
> show correct
> the
> desktop, and then after exiting the viewer, the next viewer connection
> comes
> up with the "grey screen".
>
> As I said, this is intermittent.  If I go and kill the :1 VNC
> server and
> restart it, everything will be fine until the next unexpected "grey
> screen".
>
> I have not had this problem before with Solaris SPARC or Linux.   Does
> anybody have any ideas why this intermittent behavior
> happens, and what
> to
> do to fix it?  I have searched the archives for "grey screen" postings
> and
> they generally fall into the category of 'all I get is a grey
> screen...'.
> My problem seems to be different in that it is randomly intermittent.
>
> Thanks -
>
> Joel Lieberman
> _______________________________________________
> VNC-List mailing list
> [EMAIL PROTECTED]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
> _______________________________________________
> VNC-List mailing list
> [EMAIL PROTECTED]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to