VNC 4.0 on Soalris 8 with inetd

John Aldrich JAldrich "at" covista.com
Fri Mar 11 15:32:01 2005


Ahh... Well, is there any way to force the ~/.vnc/xstartup to be read
somehow by putting it in the startup script, or using the vnc.so file? I'll
admit I don't know much about Solaris (only that it's a flavor of *nix and
that everyone I know calls it "Slowlaris" <G>) so I can't be much help.
Maybe one of the REAL experts on the list will have a suggestion. :-)
Good luck!
	John

-----Original Message-----
From: Alasdair Ferro [mailto:alasdair "at" spiratech.com]
Sent: Friday, March 11, 2005 10:25 AM
To: vnc-list "at" realvnc.com
Cc: John Aldrich
Subject: Re: VNC 4.0 on Soalris 8 with inetd


John,

I've tried CDE, Openwindows and Failsafe logins, and they all do the 
same! Bear in mind that I'm using XDMP to do the login, so my 
~/.vnc/xstartup script never gets read.

Also I'm on Solaris 8, so CDE or OpenWindows are my only options (I 
don't really want to download & install GNOME!)

But thanks for the thought!!

Alasdair

>Different window manager? :-) Seriously, ISTR reading several other CD
>complaints and switching to KDE or some other WM resolved the issue. I'll
be
>the first to admit, I don't recall exactly what the deal was or whether it
>was Solaris, Linux or BSD, but since they all use X11, it seems reasonable
>that you might at least try a different WM.
>-----Original Message-----
>  
>
>>>Since this appears to be a font problem, please can you let me know
>>>which fonts VNC needs access to on Solaris, and I'll try only specifying
>>>them.
>>>      
>>>
>>I never saw a response to this. So I thought I'd kick in my $0.02.
>>
>>    
>>
>>>>>>>>I am running VNC4.0 on Solaris 8 (2/04), via inetd. My inetd.conf
>>>>>>>>line is thus:
>>>>>>>>vnc-1152x864x24 stream tcp nowait root /space/tools/bin/Xvnc Xvnc
>>>>>>>>-inetd -query localhost -once -geometry 1152x864 -depth 24
>>>>>>>>-SecurityTypes=None -desktop="baltar-Sol8" -fp tcp/baltar:7100
>>>>>>>>                
>>>>>>>>
>>>>>This all starts with a fontpatherror. IF it is just one of the
>>>>>fontsdirectories
>>>>>in your fontpath, it should not be a problem. However, if this leaves
>>>>>no fonts
>>>>>left (all fontdirectories are wrong) then I can imagine there are
>>>>>problems.
>>>>>          
>>>>>
>>Indeed. CDE will puke if it doesn't have it's system interface fonts.
>>
>>    
>>
>>>>>Since your Xvnc call does not specify any fontpath, the windowmanager
>>>>>has to
>>>>>come with one. If they don't, there are no fonts and the
>>>>>windowmanager might
>>>>>have a problem here...
>>>>>          
>>>>>
>>The -fp option is the font path. In fact, since it's called with -fp,
>>it won't use any compiled in fonts, which I've found will usually at
>>least get you going. So my first suggestion is to remove the
>>'-fp tcp/baltar:7100' from the command inetd.conf line.
>>    
>>
>
>Tried with and without - neither give me any joy. However, having spent 
>time chasing dt & X setup scripts, I've now found which fonts paths 
>caused the errors and removed them.
>
>However, I'm still getting the Warning about "Null child found in 
>argument list to unmanage" and then "dtlogin: received signal 11", which 
>is where CDE dies I'm guessing!
>
>Any further thoughts on where to go from here??
>
>Cheers,
>
>Alasdair
>
>  
>


-- 

------------------------------------------------------------------------
Alasdair Ferro                       SpiraTech Ltd,
Product Conformance Engineer         Carrington Business Park,
mailto:alasdair "at" spiratech.com        Manchester,
Work:   +44 (0)161 776 4582          M31 4ZU,  U.K.
                                     http://www.spiratech.com
------------------------------------------------------------------------

This email and any files transmitted with it are confidential and
may be legally privileged. It is intended solely for the use of the
individual or entity to whom it is addressed. If you have received
this in error, please contact the sender and delete the material
immediately. Whilst this email has been swept for viruses, you
should carry out your own virus check before opening any
attachment. SpiraTech Ltd accepts no liability for any loss or
damage which may be caused by software viruses or interception
or interruption of this email.