INFODOC ID: 16248 SYNOPSIS: XTERMINAL: Xterminal Article Collection DETAIL DESCRIPTION: Xterminal Article Collection ---------------------------------- The SPARCclassic[TM] was last shipped in November, 1994 and EOL'd November, 1999. This article collection refers to products that are currently past their EOSL date. 1. What is an Xterminal? 2. What are Sun's[TM] Xterminals? 3. What is XDMCP and how do Xterminals use it? 4. What are the different methods for xdm to display onto Xterminals? 5. What is the Xterminal software? 6. What's the difference between the XTerminal boot host and the Xterminal session server? 7. If an Xterminal is going to use xdm does it need the Xterminal software? 8. How do you setup fonts for Xterminals? 9. Do Xterminals have Xservers? 10. Do Xterminals work across subnets? 11. How do I capture error messages from Xterminals? 12. Troubleshooting tips for Xterminals 13. Why does quitting one session from one Xterminal cause all Xterminals to reset? 14. How do I bring up CDE on an Xterminal? 15. CDE: The window manager periodically dies on Xterminals 16. How do I change the resolution of the Xterminal? 17. How do I get my Xterminals to pick up fonts from another system besides the boot host? 18. Xterminals don't work (hang) with CDE 1.2 if NOT using NIS 19. Xterminals have boot delays using xdm. 20. How to use an Xterminal without a GUI 21. Xterminal boot fails trying to get Internet/Ethernet address 22. Permissions on /tftpboot need to include read for other 23. Xterminal will not boot and does not yield any error messages 24. How to add a local printer to an Xterminal 25. Xterminal boot error: "panic: tftp_getconfig/rtrequest error=51" 26. SUNWxt installation can fail on Solaris[TM] 2.5.1 27. Different ways of booting an Xterminal 28. Xterminal complains about CDE's dt fonts in Solaris 2.6 29. Xterminals won't login to CDE, "bad font path element (#55)" errors in logfiles ============================================================================== 1. What is an Xterminal? An Xterminal is a cost effective display workstation manufactured by Sun, HP, NCR, among other vendors. It displays graphical applications that are actually running on other computers commonly called remote hostl offered later no serial, audio, or external SCSI capability 4MB of memory; although an 8MB config will be offered upgradable to diskless workstation type-5 keyboard and mouse 16" color monitor Xterminal Classic Software: boots via tftp no Xserver such as Xsun or NeWS, uses a generic Xserver no audio no DPS no serial line connect or Xremote capability 3. What is XDMCP and how do Xterminals use it? XDMCP stands for X Display Manager Control Protocol which is a standard protocol established by the X Consortium in 1989. From the end user's point of view, it maintains the connection between the Xterminal and its server in regardless of the state of the Xterminal, namely ON or OFF. When a XDMCP-compatible Xterminal is powered on, it would broadcast a request for establishing a connection to a remote host. A remote host has xdm running would reply and send a login prompt to the Xterminal. "xdm" Release 4 supports XDMCP. Therefore, if XDMCP is implemented both on the Xterminal and xdm on the remote host, an entry for the Xterminal is not required in the Xservers file. However, if neither the Xterminal nor xdm on the remote host supports XDMCP, an entry for the Xterminal should be put into the Xservers file to force a direct connection between the remote host and the Xterminal. Please read the Xservers file for more details. 4. What are the different methods for xdm or dtlogin to display onto Xterminals? Xterminals generally supply three different ways of running XDMCP: Direct Establish an XDM connection to the specified host. This requires that the name or IP address of the host running xdm be supplied. Indirect Send an indirect request for XDM connection to the specified host, which then forwards the request to another host. This requires that the name or IP address of the host running xdm be supplied. For a host running X11R4, an "Indirect" query is treated the same as a "Direct" one. For a host running X11R5, it can be configured to respond to an "Indirect" query by forwarding the request to another host or by offering a list of hosts for the user to choose from. Broadcast Broadcast the request for an XDM connection to all hosts on the subnet. This does not require a hostname or address. For most Xterminals, the first host that responds is the one that is used. For some smarter Xterminals, the X server gathers responses from all hosts on the local network and allows the user to choose one to start up on. If an Terminal doesn't connect to any host running xdm under a Broadcast query, but can connect to hosts via a Direct or Indirect query, then there is probably something wrong with the Broadcast address that you have configured the Xterminal to use. See your vendor's documentation for information on how to set the Broadcast address. 5. What is the Xterminal software? Sun provided three versions of Xterminal software, versions 1.0, 2.0 and 2.1. Sun does not sell any Xterminal software anymore because the product has been EOL'd (End of Life'd). Xterminal Software is installed on the server that will be acting as the boot host for a given Xterminal. This software allows the server to provide an ip address for the Xterminal as well as configuration files. The reason why the Xterminal software is installed on a server instead of the Xterminal itself is because the Xterminal is a dumb terminal which only contains enough memory for boot prom information. The Xterminal's Xserver is then downloaded from the boot host via the Xterminal software so that client applications can display onto the Xterminal. 6. What's the difference between the XTerminal boot host and the Xterminal session server? The Sun Xterminal boot host and the Xterminal session server can be the same system. The boot host needs to have the Xterminal software installed so it can provide the Xterminal's rarp request with an ip address at boot time. The Xterminal Session Server is there to provide the X Windows Environment for an Xterminal. This can be a separate system than the boot host depending on how the Xterminal is configured by the Xterminal Software. 7. If an Xterminal is going to use xdm does it need the Xterminal software? If the Xterminal is a Sun Xterminal then the answer is YES. If the Xterminal is actually a Sun workstation that's being used as an Xterminal then the answer is NO. The reason is that a Sun workstation already knows it's IP address and therefore just needs to get the display from the server. 8. How do you setup fonts for Sun Xterminals? Under the Xterminal software there is a GUI application called xtmgr. xtmgr has a properties window which allows you to set the path for the fonts the Xterminal should use. 9. Do Xterminals have an Xserver? All Xterminals have an Xserver which is downloaded from the Xterminal software on the boot host. The Xserver is a fully compliant X Window System X11 Revision 5 (X11R5) server. 10. Do Xterminals work across subnets? Broadcast queries are restricted to the local network or subnet. Unlike Direct and Indirect queries, you cannot use a Broadcast query to access a host through a gateway. See Item #25 below. 11. How do I capture error messages from Xterminals? Go onto the boot host and bring up the xtmgr GUI. Select properties and environment you'll see a syslog option. Once you find it click on Yes to enable it and then you should start seeing error messages in /var/adm/messages. 12. Troubleshooting tips for Xterminals 1. Always find out the exact environment setup. - What is the boot host? - Is it the Xterminal server as well? - What version of Xterminal software is running? - How many Xterminals? - Are the Xterminal on the Same subnet? - What type of connection is being used? telnet or xdm? - Do either telnet or xdm connection work? - What type of Xterminals? - Patches??? showrev -p - Any errors under /var/adm/messages? - At what point is the Xterminal failing? Get Description of the state of the Xterminals. 2. Enable syslog if it's not already enabled. 3. What is the command used to boot the Xterminal? 4. You can run a snoop to see what the Xterminal and the servers are doing. snoop -rarp 13. Why does quitting one session from one Xterminal cause all Xterminals to reset ? The most likely reason for the resource: DisplayManager*reset in the $OPENWINHOME/lib/xdm/xdm-config file is being set to: $OPENWINHOME/lib/xdm/Xreset If the entry does exist in the xdm-config file: DisplayManager*reset: $OPENWINHOME/lib/xdm/Xreset it should be changed to: DisplayManager._0.reset: $OPENWINHOME/lib/xdm/Xreset The xdm process should be restarted. 14. How to start CDE on Xterminals CDE works nicely with Sun's Xterminal line. The InstallGuide has a Using Xterminals section, around page 25 (depending on the doc's revision). You can find an online copy of this guide in the CDE Application Mgr's Information Folder (on CDE system's installed with Developer's cluster). This guide is also in the CDE answerbook. The abbreviated answer is, on the Xterminal's property setup, select: Use XDM XDM connection : indirect to Local Window Mgr : None On the Xterminal's Fonts setup dialog: Add Font path of /usr/dt/config/xfonts/C (for C local) to a workstation exporting the installed CDE area. Add the appropriate font paths for European or Asian locales. (Note that this font path is installed from the package SUWdtft, which is available in Solaris 2.4 and 2.5.X. It is not available after Solaris 2.5.1. For Solaris 2.6, you may be able to use the font path of /usr/openwin/lib/X11/fonts/F3bitmaps, although this has not been tested.) Restart the Xterminal and CDE's chooser screen will appear. Then double-click on the name of the workstation that you wish to log in to. 15. CDE: The window manager periodically dies on Xterminals CDE consistently dies on all Xterminals connected to a specific server after running for a time period - usually in the range of 10 to 15 minutes. In addition, these messages appear in ~/.dt/startlog: ... --- /usr/dt/bin/Xsession starting... fbconsole: open /dev/console: Permission denied --- Xsession started by dtlogin ... and these messages appear in ~/.dt/errorlog: ... Workspace Manager: I/O error on display:: ... The Xterminal's server does not have a graphics monitor on it. Rather, it has serial console connected or no monitor at all. SOLUTION SUMMARY: The problem is that the server console doesn't have an associated framebuffer. CDE is attempting to start up the X Server on a server that has no framebuffer, and failing. When that happens the CDE processes die, bringing down all the CDE Xterminal connections to the server. To avoid this problem, modify Xservers as follows: 1. cp /usr/dt/config/Xservers /etc/dt/config 2. Comment out the following line in /etc/dt/config: :0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner to: # :0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner 16. How do I change the resolution of the Xterminal? How do I change the resolution on an X-Terminal running 2.1, for example from 75x75dpi to 90x90dpi. Edit the sunxt_config file either in /tftpboot or in the sub-directory /tfptboot/HOSTID_CFG and add the following line: screen_resolution 90dpi 17. How do I get my Xterminals to pick up fonts from another system besides the boot host? Problem: A customer has an Xterminal 1, NFS server(boot host), and a PC. The customer wants to have the fonts and rgb from the PC instead of the boot host. Solution: The correct way to do this is to bring up xtmgr on the boot host, then modify the Xterminal properties. Go under fonts and enter the PC hostname and the path to the fonts found on the PC. Do the same for the rgb, go to the environment properties. Change the Color Server to the PC hostname, specify the path name to the rgb file of the PC, then hit apply and add. NOTE: All these modifications should be done on the boot host. The NFS server should not be turned off at all if the xterminal will be used. The Solution given above will not work if the boot host isn't up and running. The Xterminal is dependent on the boot host during boot up. 18. Xterminals don't work (hang) with CDE 1.2 if NOT using NIS Xterminals like hamlet, Xterminal1, NCD, and Tektronix don't come up with CDE 1.2. if NOT running NIS. After booting, the terminal hangs. Dtlogin does not show up. This happens at sites where no NIS is running as well as at sites where the NIS domainname equals the DNS domainname. The assumption being made in CDE is that there is always NIS running and that the NIS domainname has an additional prefix over the dns domainname. This is certainly the case at most sites, but this is not guaranteed. The interesting lines are in /usr/dt/config/Xstartup: # Append Font Server to tail of path. # Will server any "-dt-" fonts not found on the remote machine. # if [ -x /usr/openwin/bin/fs ]; then $XDIR/xset fp+ tcp/`/usr/bin/hostname`.`/usr/bin/domainname | /usr/bin/cut -d. -f2-`:7100 fi and /usr/dt/bin/Xsession. # Append Font Server to tail of path. # Will server any "-dt-" fonts not found on the remote machine. # if [ -x /usr/openwin/bin/fs ]; then $XDIR/xset fp+ tcp/`/usr/bin/hostname`.`/usr/bin/domainname | /usr/bin/cut -d. -f2-`:7100 fi Comment out the mentioned lines. 19. Xterminals have boot delays using xdm A customer sees huge delays in booting their Xterminals. When the Xterminal attempts to boot, it cycles between the large Sun logo and a blank screen. After a few cycles, it reboots and continues the same cycling. Eventually the Xterminal boots up. In this case, xdm 3.4 was running and controlling the Xterminals. After the Xterminals booted, xdm was attempting to bring up the xdm login widget, but couldn't. What happened: Xdm needs to create an authorization file in /var/tmp for each Xterminal/host it controls. It must create this file before the xdm login widget can be displayed. It was having problems creating this file. The following error was logged to the xdm-errors file every time xdm failed to create the authorization file: Cannot open server authorization file This authorization file could not be created because a unique filename could not be found. The unique file name consists of 13 digits. Below are what is stored in each digit. - digit 1 ==> is an 'A' - digit 2-6 ==> are taken from the first 5 digits of the xdm clients host name. - digit 7 ==> is a '-' - digit 8 ==> is a letter between a and z - digit 9-13 ==> a unique 5 digit number generated off the pid of the main xdm process. As you can see, the only unique parts of this file name are the 5 digits ( digits 2-6 ) that come from the Xterminals hostname, and digit 8 ( the letter a - z ) The last 5 digits ( digit 9-13 ) will always be the same because they are generated off the main ( or parent ) xdm process id. If you have Xterminals/hosts with identical letters in the first 5 digits, *and* you have more then 26 hosts (a - z ), then the above error message will be generated. The Xterminal should have come up after the error was generated, but it didn't. But changing the Xterminal names to be unique in the first 5 digits fixed this problem. 20. How to use an Xterminal without a GUI If xtmgr causes a core dump or if there is no GUI environment to run xtmgr, an Xterminal still can run by: At the Boot Host: 1. Install the Xterminal software (V2.1) in the Boot Host's /opt directory. 2. Enter the Xterminal's IP address and hostname in the /etc/hosts file. 3. Enter the Xterminal's ethernet address and hostname in the /etc/ethers file. 4. Enter this line in /etc/dfs/dfstab: share -F ufs -o ro /opt/SUNWxt/v2.1 then run: shareall At the Xterminal: 1. Turn it on only after the Boot Host is setup as above. 2. Press Stop-A, and at the PROM level (ok prompt) type: ok boot net:,sunxt_kernel.v2.1, sunxt_kernel.v2.1 is the kernel that Xterminal needs to locate in order to boot. Normally, adding an Xterminal in xtmgr will do just that, identifying the kernel for booting. If xtmgr does not run, then booting with the boot command that includes the kernel file will work also. If xtmgr causes core dump or there is no GUI environment to run xtmgr, Xterminal still can run by: At Boot Host: - Install Xterminal software in Boot Host /opt directory. - Enter Xterminal IP address and name in /etc/hosts file. - Enter Xterminal ether address and name in /etc/ethers file. - Enter this line in /etc/dfs/dfstab share -F ufs -o ro /opt/SUNWxt/v2.1 then run shareall. At Xterminal: - Turn it on only after Boot Host is setup as above. - Press stop-A, enter PROM level, type ok boot net:,sunxt_kernel.v2.1, sunxt_kernel.v2.1 is the kernel that Xterminal needs to locate in order to boot. Normally, adding Xterminal in xtmgr will do just that:identifying the kernel for booting. If xtmgr does not run then booting with the boot command that includes kernel file will do too. 21. Xterminal boot fails trying to get Internet/Ethernet address When booting a Xterminal which is located on one subnet and the Boot Host is located on other subnet (or domain), the message that appears is: Trying to get Internet/Ethernet Address... Contact your system administrator to see if a Boot Host and the network are set up correctly This indicates that a timeout occurred while waiting for an ARP/RARP packet. If booting from a Boot Host, make sure to enter the IP address of the server on the same subnet with the Xterminal, not the IP address of the server on the same subnet with the Boot Host. Find the IP address of the server by going to any system on the same subnet as the Xterminal and type this line (Examples shown are for the NIS name service): # ypwhich will show server name. Then find the IP address of the server by typing : # ypmatch hosts This will show the IP address of the server on the Xterminal's subnet. Finally, type the following boot command on the Xterminal: ok boot net:,,, 22. Permissions on /tftpboot need to include read for other A customer was installing an Xterminal (Classic X, but this will apply to Xterm1 also). After completing the xtmgr steps, the customer tried to boot the Xterm and got an error; "tftp host responds with error 2" on the Xterminal. The customer's root user was set up to create files with permissions of 600. The /tftpboot directory, subdirectories and files were owned by root and had permissions of 600. "Other" had no read permission, so tftp couldn't access and failed to load bootfile to Classic X. Fix: Run the command; chmod -R o+r /tftpboot (note the capital R). to allow everyone to have read permission to the /tftpboot directory and all directories and files below. This allowed the Xterminal to boot. 23. Xterminal will not boot and does not yield any error messages Snooping the Xterminal client on the net yields: "gets ICMP destination unreachable (bad port)" Upon further investigation, the problem was in the tftp entry of /etc/inetd.conf file. By default the entry in /etc/inetd.conf for tftp should be: tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot But this machine's entry was: tftp dgram udp nowait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot Changing the "nowait" entry to "wait" fixed the problem and the Xterminal now boots. 24. How to add a local printer to an Xterminal In order to add a printer to an Xterminal's parallel port, either Sun's or third party, they need to get the Xterminal's device file for that particular port. Once we have the device file then we can add it via Admintool[TM] or from the command line. lpadmin -p -v -T unknown -I any enable accept 25. Xterminal boot error: "panic: tftp_getconfig/rtrequest error=51" [1.] Ensure that the Xterminal has been configured properly. Always find out the exact environment setup. o What is the boot host? o Is it the Xterminal server as well? o What version of Xterminal software is running? o How many Xterminals? o Is the Xterminal using a gateway to the server? o What type of connection is being used? telnet or xdm? o Do either telnet or xdm connection work? o What type of Xterminals? o Patches??? showrev -p o Any errors under /var/adm/messages? o At what point is the Xterminal failing? Get Description of the state of the Xterminals. o Enable syslog if it's not already enabled. o What is the command used to boot the Xterminal? o You can run a snoop to see what the Xterminal and the servers are doing. snoop -rarp [2.] Xterminals can be configured to boot through a gateway. If the server and the Xterminal are not on the same network segment, a gateway IP address which resides on the same subnet as the Xterminal MUST be provided. See details regarding the use of the gateway IP in item 3 below. [3.] Check the command you are using to boot the Xterminal. You can either manually boot the Xterminal from the "ok prompt" also known as the OBP (Open Boot Prom) level by typing in the whole "boot net" parameter. Example: ok boot net:,,, OR: You can set the boot-device parameter at the OBP level to be the actual "boot net" line. Example: ok printenv boot-device Output will be: boot-device net ok setenv boot-device net:,,, ok reset ok printenv boot-device Output will be: boot-device net:,,,,,, INCORRECT NETWORK SETUP FOR THE XTERMINAL: Example: boot-device is set to: net: 157.95.36.211,,157.95.37.214,157.95.36.10 wherein the IP Addresses are translated as: net:,,, NOTE: The above example is an incorrect network setup for the Xterminal. The boot_host addr and gateway_addr should not be the same address; the gateway_addr *must* be an address on the same subnet as the X terminal (which in the example given it clearly is not). BE CAREFUL OF BOOTING THROUGH GATEWAYS: o To boot thru a gateway you must specify the IP address of the terminal, server and gateway; you can't use RARP to get your IP address thru a gateway. o The gateway IP address must be on the same subnet as the Xterminal. Failure to follow these will result in the error: "panic: tftp_getconfig/rtrequest error=51". 26. SUNWxt installation can fail on Solaris 2.5.1 The installation of SUNWxt on Solaris 2.5.1 fails with pkgadd postinstall script errors: (some lines deleted in the example) /opt/SUNWxt/v2.1/sunxt_dbgknl.v2.1 /opt/SUNWxt/v2.1/sunxt_kernel.v2.1 /opt/SUNWxt/v2.1/util/mkfontdir /opt/SUNWxt/v2.1/xt_install /opt/SUNWxt/v2.1/xterm.mib.v2.1 verifying class /opt/SUNWxt/v2.1/Xdefault/fonts/6x13.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/cursor.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/luBIS12.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/luBS12.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/luIS12.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/luRS12.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/lutRS12.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/ncenB14.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/olcursor.pcf.Z /opt/SUNWxt/v2.1/Xdefault/fonts/olgl12.pcf.Z ## Executing postinstall script. Segmentation Fault pkgadd: ERROR: postinstall script did not complete successfully Installation of failed. Trussing the postinstall script reveals that it is the binary /opt/v2.1/xt_install that dumps core. To get SUNWxt to install: 1. Make sure that the hostname is a short one, i.e. uname -n returns something like "xtsrv"and not "xterminalserver.foo.bar.com" See the man page for sys-unconfig to change the hostname. 2. If you want to truss the postinstall script, you will have to change the checksums in the pkgmap file. Copy the SUNWxt package directory from the CDROM to a writable directory then edit /space/Xterminal_2.1_704-4906-10/SUNWxt/pkgmap and change the checksums line for 1 i postinstall 1732 7581 786749221 to the values *after* you modified postinstall for the truss command, using the sum and wc -l command. # sum install/postinstall 7583 4 install/postinstall # wc -l install/postinstall 68 install/postinstall # wc -c install/postinstall 1733 install/postinstall So the new line should be: 1 i postinstall 1733 7583 786749221 Save the file, then run pkgadd. 27. Different ways of booting an Xterminal Different ways of Booting and Configuring an X-Terminal: Boot through path set in boot-device PROM variable: ok boot Boot from RARP server: ok boot net Boot from specified kernel: ok boot net:,sunxt_kernel.v2.x, Boot through gateway: ok boot net:,,, Boot to specific boot host: ok boot net:,, Setting the boot path: ok setenv boot-device Configuring an X-Terminal for automatic boot from net: ok setenv boot-device net ok reset 28. Xterminal complains about CDE's dt fonts in Solaris 2.6 Since upgrading my Sun system to Solaris 2.6/CDE 1.2, my Xterminals show a font problem when I start certain applications on them. For example, starting Matlab 5.2 I get the following warnings: Warning: Cannot convert string "-dt-interface user-medium-r-normal-m-*-*-*-*-*-*-*-*-*" to type FontStruct Warning: Missing charsets in String to FontSet conversion What is causing this? The Xterminals are getting fonts from a font server that doesn't provide dt fonts. Serve the dt fonts to the Xterminals from a font server on a Solaris 2.6/CDE 1.2 system. To do this, login to the Sun on the console in CDE. In any terminal window type: /usr/openwin/bin/xset -q Keyboard Control: auto repeat: on key click percent: 0 LED mask: 00000000 auto repeating keys: 00faaf8becff67f2 ff7bf0ff1ff89f03 1100000000000000 0000000000000000 bell percent: 50 bell pitch: 400 bell duration: 100 Pointer Control: acceleration: 2/1 threshold: 4 Screen Saver: prefer blanking: yes allow exposures: yes timeout: 900 cycle: 600 Colors: default colormap: 0x3b BlackPixel: 0 WhitePixel: 16777215 Font Path: /usr/openwin/lib/X11/fonts/F3/,/usr/openwin/lib/X11/fonts/F3bitmaps/, /usr/openwin/lib/X11/fonts/Type1/,/usr/openwin/lib/X11/fonts/Speedo/, /usr/openwin/lib/X11/fonts/misc/,/usr/openwin/lib/X11/fonts/75dpi/, /usr/openwin/lib/X11/fonts/100dpi/ Bug Mode: compatibility mode is disabled skywalker$ --- The important thing is the "Font Path". Suppose the Sun machine is called whizbang. Try logging on the Xterminal and type in a terminal window: /usr/openwin/bin/xset +fp tcp/whizbang:7100/all (If you changed the port for the fs fontserver, you need to change the 7100 port number to the appropriate value.) (You can also use the original "Font Path" information to plug into the previous command if you do not want to use all the fonts: /usr/openwin/bin/xset +fp tcp/whizbang:7100/usr/openwin/lib/X11/fonts/F3/ It is important that afterwards you check the settings with the xset -q command. If you want to do this for every user permanently, then you need to consult the vendor of your Xterminals on how to set the fontpath permanently. Also, check out /usr/dt/config/Xsession.d/0015.sun.env line 117 and check out /usr/dt/bin/Xsession Please copy these files to /etc/dt/config and /etc/dt/bin and edit them there ONLY. 29. Xterminals won't login to CDE, "bad font path element (#55)" errors in logfiles Using Xterminals (NCD and/or HP, etc.) and trying to connect to a Sun machine's dtlogin process, but cannot login to CDE. It just display an hourglass and hangs and finally I am returned to the dtlogin screen. /var/dt/Xerrors and my $HOME/.dt/errorlog says something like: xset: bad font path element (#55), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax What do I do now? *** Sun supports third-party Xterminal connections to the Sun machine on a best-effort basis. Xterminal 2.1 software from Sun is not supported on Solaris 2.6. *** as root mkdir -p /etc/dt/config cp /usr/dt/config/Xsetup /etc/dt/config edit /etc/dt/config/Xsetup and and check for the lines containing any references to /usr/dt/config/xfonts and /etc/dt/config/xfonts and comment them all out. Save the file. Additionally, you may even find it necessary to comment out all references to /usr/dt/config/xfonts and /etc/dt/config/xfonts from /usr/dt/bin/Xsession. Make sure you have a backup copy of Xsession *before* making any changes to the file. Also record this change in your system administration logbook. APPLIES TO: Hardware ATTACHMENTS: