> Date: Mon, 10 Jun 2002 10:19:04 +0200 > From: "Beerse, Corni" <[EMAIL PROTECTED]>
> xfstt??? What's that (I have not found time to get a SuSE 8 copy.) X font server for TrueType fonts (which VNC apparently can't handle in the font path). > The last line adds the local font server. Best to choose between the > fontserver and a fully specified fontpath. My idea, only specify the > fontserver here (-fp tcp/localhost:7101) See above. I'm not sure if xfstt also serves bitmap and Type1 fonts (if so, then that might be OK). There would probably be a tradeoff between speed and memory use. > Other users: read the console fontpath from the local xserver with `xset -q` > and specify that here. I found "-fp unix/:7100" xset -q will list directories that VNC can't handle (e.g truetype). Port 7100 is typically xfs (X font server for bitmap fonts). I grabbed the lines from /etc/X11/XF86Config (this is version 4.2) and put them in vncserver, then ran it. Then examined the log file to see which ones it complained about and removed them from vncserver, also added the one for xfstt. If you use xset -q from within a VNC session, don't forget to also specify -display host:0 ! > Some alternate routes to accuire similar behavoure: > For XF86 version 4 users: http://xf4vnc.sourceforge.net/. This includes the > acceleration of the standard X11 server. Problem here (for the momemt): Only > linux, Only intel, not all display drivers are supported at the moment. XF86 is difficult enough to get set up correctly, and vendor updates might override a driver substitution. Also, xf4vnc either uses no password or a specific user's VNC password, whereas my method will use the VNC password for whatever user is logged in at the console. Here, X objects to the syntax of some of the lines given at the URI: Option "rfbport" 5900 Option "httpport" 5800 I get error messages like: Parse error on line 164 of section Device in file /etc/X11/XF86Config "5800" is not a valid keyword in this section. Apparently, the lines should be Option "rfbport" "5900" Option "httpport" "5800" And some of the references to input and screen sections may need to be revised to match the relevant entries in XF86Config. ----- Additional caveats not mentioned in the original: Some care is required when running X programs, as they will be running with Xvnc. For example, running SuSE's SaX2 (X configuration utility) would probably be a very bad idea as it would overwrite XF86Config. While this may be unrelated to the VNC changes, here, the "logout" item in the KDE (v3) menu unfortunately doesn't end the session. However, the button on the lock/logout applet does work. An alternative way to end a session is to send a SIGTERM signal to the Xvnc process. Other resources: An article by Jeremy D. Impson appeared in the January 2002 issue of Linux Journal. It takes a somewhat different approach. While the article states "The scheme we discuss can work on any Linux distribution", SuSE is different enough from Red Hat 7.1 that the method outlined in the article definitely does not work for SuSE (primarily because of the way SuSE provides a session selection). _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
