The problem was:
> I'm trying to setup 19" VXT-2000+ X-terminals using the vxtex (clientless)
> software on Alpha 3000/600s running OSF/1 2.0. (Upgrading the OS isn't an
> option because of the requirements of commercial telemetry software running
> on them.) I didn't have a problem changing from vxt to vxtex, but I'm
> having absolutely ZERO luck configuring the font paths. No matter what I
> put in the font path field in the VXT's setup screen, when I bring up the
> setup screen again after accepting the changes, it complains that the font
> path is invalid and that it's using its (tiny) internal fonts instead. Any
> ideas? Is there anyone else out there running VXTs in this way, rather
> than with the (memory-hog) client mode software? (I'll summarize as
> appropriate.)
I received four suggestions from:
Andy Phillips <atp_at_mssly1.mssl.ucl.ac.uk>
"Andrew Brennan, Lackey-at-large" <BRENNAN_at_HAL.HAHNEMANN.EDU>
pfs_at_mimuw.edu.pl (Piotr Filip Sawicki)
Hellebx Knut <bgk1142_at_bggfu2.nho.hydro.com>
They were all good suggestions. Unfortunately, my problem was with the
tftp configuration. We have a soft link from /tftpboot to /usr/tftpboot
and I was using /usr/tftpboot in the font path on the VXT terminal.
However, when I finally got around to checking the /etc/inetd.conf, I
realized that the directory option for configuring tftpd was restricting
valid tftp requests to start with /tftpboot. While /usr/tftpboot was the
same directory as /tftpboot, the tftpd saw it differently than /tftpboot
and rejected it as an invalid tftp request. A silly mistake on my part.
Sorry all and thanks again! Below are the suggestions that I received.
===============================================================
| Juan Rivero (rivero_at_use1.eglin.af.mil) TYBRIN Corporation |
| Eglin AFB: (904) 882-9742 Shalimar, Florida |
===============================================================
=====================================================================
From: Andy Phillips <atp_at_mssly1.mssl.ucl.ac.uk>
yep,
had this problem. Bit of a pain isn't it?
still. My solution was this.
copy all the fonts into one directory;
e.g.
cp /usr/local/vxt/fonts/75dpi/* /usr/local/vxt/fonts/allfonts
cp /usr/local/vxt/fonts/100dpi/* /usr/local/vxt/fonts/allfonts
:
do a mkfontdir on this directory.
put the tftpd line in the inetd.conf (for the above example)
-------
# tftp daemons for X terminals.
tftp dgram udp wait root /usr/sbin/tcpd tftpd -d /usr/local/vxt
--------
The tcpd is tcp wrappers, remove this if you dont have tcp wrappers.
make inetd re-read its conf
kill -HUP `ps ax | grep inetd | cut -c0-5`
now got to the X terminal. bring up the config window, and enter in the
tftp font path
/usr/local/vxt/fonts/allfonts/fonts.dir
That should be it. Works for us.
I am still a little peeved at the memory hogging nature of the
VXT s/w, and that the VXTEX s/w can't do routing via a gateway.
hope this helps.
andy
--
atp_at_mssly1.mssl.ucl.ac.uk Andy Phillips
atp_at_mssl.ucl.ac.uk Mullard Space Science Laboratory,
phillips_at_isass1.solar.isas.ac.jp Dept. Space and Climate Physics,
mssly1::atp University College London.
=====================================================================
From: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_HAL.HAHNEMANN.EDU>
Perhaps you have a protection problem along the path to the font dirs?
I'm using the configuration you've described (although a less powerful
Alpha at the end :^) and have been doing so for at least 6 months. I
think my font specification is something like vxt/fonts/... or maybe
/tftpboot/vxt/fonts/... - I'd have to disconnect from the network to
see for sure, though.
I have *not* tried loading from an InfoServer - but that's due to the
fact that the IS hasn't been completely configured yet.
andrew. (brennan_at_hal.hahnemann.edu)
=====================================================================
From: pfs_at_mimuw.edu.pl (Piotr Filip Sawicki)
1. Load vxtex and wait for xdm.
2. Log in ignoring complaints about fonts.
3. Call in vxtex setup window (F3 or Ctrl-F3 or Ctrl-Alt-F3).
4. Set *NOT* the font path, but the path to fonts.dir files you need (!!!).
For example, if you want to use fonts from directory named
"/usr/local/lib/Xfonts/100dpi", put this in the appropriate field:
/usr/local/lib/Xfonts/100dpi/fonts.dir
Be careful, however, with vxtex. Xdm pings the terminal time to
time to see if it is still alive, and very busy vxtex tends to
respond far too late. As a result, you may find yourself logged out
in the least expected moment.
Better try to set up OSF as a MOP server for VXT 2000 (some say
it is possible --- but don't ask me how).
fi.
--
'vi'ssic Park: Come and see those who did not find time to learn emacs!
=====================================================================
From: Hellebx Knut <bgk1142_at_bggfu2.nho.hydro.com>
Hello !
Are you sure that the font directories have the correct (and readable)
font.{dir,alias} files and that the directories themselves are world
readable (see 'man mkfontdir') ??
=====================================================================
Received on Tue Feb 21 1995 - 11:50:08 NZDT