-------------------------------------------------------------------------- Tarantella Enterprise 3 (version 3.1) -------------------------------------------------------------------------- Read this to find out how to install Tarantella on your system. -------------------------------------------------------------------------- Contents -------------------------------------------------------------------------- - What's on the CD - Before you install - Upgrading from version 3.0x to version 3.1 of Tarantella - Recommended/required operating system modifications Caldera OpenLinux eServer 2.3+ Compaq Tru64 UNIX v5.0A HP-UX 11.00 IBM AIX 4.3+ Linux kernel 2.2+ (all distributions) SCO OpenServer Release 5.0.5+ SPARC Solaris 2.6+ TurboLinux 6.0+ UnixWare 7.1.1+ - Additional kernel tuning for the Tarantella Mainframe Connectivity Pack - Installing Tarantella - Configuring a web server for use with Tarantella - Where to look for more information -------------------------------------------------------------------------- What's on the CD -------------------------------------------------------------------------- This CD contains: - For each supported system, one shx archive containing the Tarantella Base Component. - A number of subdirectories containing shx archives for additional Tarantella packs: mcp Tarantella Mainframe Connectivity Pack acp Tarantella AS/400 Connectivity Pack tsp Tarantella Security Pack font Additional font packages - A /native subdirectory containing a Native Client archive for each supported system. About shx archives -------------------------------------------------------------------------- Files with the extension "shx" are self-installing archives (SHell eXecutables). Each shx archive contains one or more packages, which are the main self-contained parts of Tarantella. These are UNIX SVR4 packages: the shx file acts as a wrapper around the UNIX pkgadd command. For those versions of UNIX that don't support the SVR4 package mechanism, we've included that too: installed automatically as part of the shx archive. You use the same archives whether you're installing Tarantella for the first time, or upgrading from an earlier version. -------------------------------------------------------------------------- Before you install -------------------------------------------------------------------------- The Tarantella CD insert contains a pre-installation checklist to follow before installing Tarantella. We recommend that you follow this checklist carefully before trying to install Tarantella. IMPORTANT: If you are upgrading from the original release of Tarantella Enterprise 3, you don't need to uninstall Tarantella first. Your existing configuration will be preserved when you run Tarantella Setup. -------------------------------------------------------------------------- Upgrading from version 3.0x to version 3.1 of Tarantella -------------------------------------------------------------------------- Upgrade backup directories [512465] -------------------------------------------------------------------------- The following directories are backed up during the 3.1 upgrade: etc/templates etc/data var/serverresources/expect var/docroot var/ens Backups are numbered with the full version number appended (for example, etc/data.3.01.905). If you change a file in your installation and want to return to the original version, copy it from one the backup directories. Note: var/docroot.3.0x is a sparse backup consisting of cgi-bin/, *.html and resources/. Windows Connectivity Pack [517191] -------------------------------------------------------------------------- The Windows Connectivity Pack is now installed automatically when you install the Tarantella Base Component. However, you must explicitly uninstall the Windows Connectivity Pack before upgrading to this release, using the "tarantella uninstall ttawcp" command. If you don't uninstall this package before upgrade, some keymap files are not upgraded successfully. This will mean that users can launch applications but not type into them. If this happens, copy the keymap files from /etc/templates/etc/data/keymaps to /etc/data/keymaps. Reinstalling add-on packs [515577, 516351] -------------------------------------------------------------------------- All add-on packs are uninstalled during the 3.1 upgrade and you will need to reinstall 3.1 versions. This does not apply to Solaris 2.6+ systems, where add-on packs will need to be manually removed and reinstalled. Note: To preserve your current pack configuration (for example, the contents of tsp/certs and wcp/licenses), you *must* reinstall Tarantella in the same directory. Reconfiguring ports [517186] -------------------------------------------------------------------------- Any port attributes configured using the tarantella config edit command are set back to their default values during the 3.1 upgrade and will need to be reconfigured. Upgrading arrays [514839] -------------------------------------------------------------------------- We recommend that you upgrade an array by gradually emptying the 3.0x array and building a new 3.1 array: 1 Detach a secondary server from array 1. This will be the new primary in array 2. 2 Upgrade this new primary server to 3.1. 3 For each of the remaining secondary servers in array 1: - Detach it from array 1. - Upgrade it to 3.1. - Join it to array 2. 4 Upgrade the last (primary) member of array 1 to 3.1. 5 Join the last (primary) member of array 1 to array 2 as a secondary server. 6 Remaster array 2 so that the original primary server in array 1 becomes the primary server in array 2. IMPORTANT: In a mixed array, the primary server is allowed to be newer than its secondaries, but not vice versa. -------------------------------------------------------------------------- Recommended/required operating system modifications -------------------------------------------------------------------------- We recommend modifications for the following operating systems: - Caldera OpenLinux eServer 2.3+ - Compaq Tru64 UNIX v5.0A - HP-UX 11.00 - IBM AIX 4.3+ - Linux kernel 2.2+ (all distributions) - SCO OpenServer Release 5.0.5+ - SPARC Solaris 2.6+ - TurboLinux 6.0+ - UnixWare 7.1.1+ -------------------------------------------------------------------------- Caldera OpenLinux eServer 2.3+ [511408] -------------------------------------------------------------------------- Due to a known problem in the pthreads library regarding support for the IBM JDK version 1.1.8, rebuilt glibc libraries are required for this platform. The updated package, glibc-2.1.2-2S (Ref. #000201-0047), can be found on the Caldera FTP site: ftp://ftp.calderasystems.com/pub/updates/eServer/2.3/001/RPMS You can install the relevant RPM files using the Caldera package manager. Without the rebuilt glibc libraries, the installation proceeds correctly until it attempts to start the Tarantella server. The installation then exits, displaying an error message. -------------------------------------------------------------------------- Compaq Tru64 UNIX v5.0A [514814] -------------------------------------------------------------------------- You may need to install patch T64V50AAS0002-20001004 from Compaq. -------------------------------------------------------------------------- HP-UX 11.00 [514992] -------------------------------------------------------------------------- You should install the following patches (see http://www.hp.com/products1/ unix/java/infolibrary/patches.html): XSWGR1100 General release bundle containing many patches PHCO_22314 PHKL_23002 PHCO_22453 PHCO_21845 PHKL_23183 PHKL_22432 PHKL_22589 Note: PHCO_19666, PHKL_18543 and PHKL_20016 are also required but should be contained in XSWGR1100. The following additional patches are recommended if you are using AWT: PHSS_17535 PHSS_20863 PHSS_21982 PHSS_22341 PHSS_22946 PHNE_22086 To determine which patches have been installed on your machine, login as root and run /usr/sbin/swlist -l product. Kernel tuning -------------------------------------------------------------------------- If you are seeing "OutOfMemoryException" in the JServer log files (around thread start() or run() methods) you may need to increase the thread tunables. On HP-UX 11.0 the default thread mechanism is kernel threads. Set the kernel tunables (max_thread_proc, nkthread, for example) so that the application can be run with the kernel-threaded JVM. The tunables of interest are: max_thread_proc The maximum number of threads in a single process. This needs to be large enough to accommodate all of the threads in the Java application plus the handful of additional threads in the virtual machine itself. nkthreads The maximum total number of kernel threads on the system. This needs to be large enough to accommodate all of the applications that will be run simultaneously on the system plus all of the kernel threads needed by the kernel. Typically this parameter is a function of nproc and an expected average number of threads per process. Note: You can alternatively run the program with the green threaded JV with the -green option (without changing the kernel parameters). For more information, see http://www.hp.com/products1/unix/java/java1/ jdk_jre/faq.html. -------------------------------------------------------------------------- IBM AIX 4.3+ [512432] -------------------------------------------------------------------------- To use the CPU-based load balancing feature of Tarantella, you must install the optional bos.acct and bos.perf packages. You can find these packages on your AIX distribution CD. -------------------------------------------------------------------------- Linux kernel 2.2+ (all distributions) [513867] -------------------------------------------------------------------------- On Linux systems, each thread is mapped to a separate process (unlike on UNIX systems). As Tarantella is a multi-threaded server, you'll see a large number of processes in process listings and you may need to increase the number of processes supported by the kernel. The Red Hat Linux 6.2 kernel and kernels compiled with the kernel-source-2.2.14-5.0 RPM support 2560 processes by default. This process limit should support approximately 1000 users per server, if each user runs one application. To increase the number of processes your kernel supports, see your Linux vendor's web site for details. File descriptors and inodes -------------------------------------------------------------------------- You should increase the maximum number of file descriptors and inodes. The inode limit should be three times the file descriptor limit. On some Linux systems (for example Red Hat Linux 6.2) you would append the following lines to /etc/rc.d/rc.local: echo "16384" > /proc/sys/fs/file-max echo "49152" > /proc/sys/fs/inode-max On Caldera OpenLinux eServer 2.3+, edit the /etc/system.cnf file and change the CONF_INIT_MAX_FILES and CONF_INIT_MAX_INODES parameters to 16384 and 49152 respectively. Using Linux as an application server -------------------------------------------------------------------------- If you use Linux as an application server, each emulator session requires one pseudo-tty. For example, 50 users running 10 applications each on one application server requires 500 pseudo-ttys. See http://linuxperf.nl.linux.org/general/common.html for tips on performance tuning. -------------------------------------------------------------------------- SCO OpenServer Release 5.0.5+ [511407, 515602] -------------------------------------------------------------------------- You must install the Binary Compatibility Module 7.1.1 for SCO OpenServer Release 5, which you can download from http://www.sco.com/download. For SCO OpenServer Release 5.0.5 systems, you should also install the following patches (available from your support provider or from SCO Support Services, http://www.sco.com/support): rs505a Release Supplement 505A oss471f Intel Pentium Microcode Driver oss497c Core OS Supplement oss600a Year 2000 Supplement Newer patches may become available over time. Kernel tuning -------------------------------------------------------------------------- We recommend you tune the kernel for optimal performance by raising the following parameters to the specified values: NOFILES 4096 MAXUP 1024 NSTREAM 8192 NSTRPAGES 1000 NUMSP 1024 -------------------------------------------------------------------------- SPARC Solaris 2.6+ [513869] -------------------------------------------------------------------------- You should install the following patches as appropriate for your Solaris version (see http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access). These are the recommended patches for running a Java Virtual Machine. Version Patch ID Status Description Solaris 2.6 107733-06 required Linker Patch 105568-17 required Libthread Patch 105210-27 required LibC Patch 106040-13 required X Input and Output Method Patch 105633-38 required OpenWindows 3.6: Xsun Patch 106409-01 required Fixes the Chinese TrueType fonts 108091-03 required Fatal error in ISO8859-01 Locales 106842-09 required Euro currency support 106841-01 required Keytables Patch 105181-20 required Kernel Update (socket close/hang) 105669-10 recommended CDE 1.2: libDTSvc Patch (dtmail) 105284-33 recommended Motif 1.2.7: Runtime library patch 105591-09 required C++ shared library patch 106125-09 required Patch for patchadd and patchrm Solaris 7 106980-10 required Libthread Patch 107636-03 required X Input and Output Method Patch 108376-07 required OpenWindows 3.6.1 Xsun Patch 107153-01 required Replaces bad font in zh.GBK locale 106541-11 required Kernel update 107544-03 required To be used with Kernel update patch 109104-01 required To be used with Kernel update patch 106950-09 required Linker Patch 106327-08 required Shared library patch for C++ 106300-09 required Patch for C++ 107081-20 required Motif 1.2 and Motif 2.1 patch Solaris 8 108940-07 required Motif 2.1 patch -- available soon from SunSolve Multi-processor systems -------------------------------------------------------------------------- Install one of the following additional patches on multi-processor systems: Solaris 2.6 105780-05 Solaris 7 106944-03 Solaris 8 109454-01 (currently restricted to Sun contract customers) Newer patches may become available over time. Supporting a large number of users per Tarantella server -------------------------------------------------------------------------- Solaris 7+ only: To support a large number of users on a Tarantella server, increase the hard limit on the number of file descriptors. We recommend you do this to support more than 100 users. Add this line to your /etc/system file (make a backup first): set rlim_fd_max=4096 You need to reboot for the change to take effect. See "man -s 4 system", and http://sunsolve.sun.com/pub-cgi/retrieve.pl?type=0&doc=infodoc/21622 for advice on tunables. This document recommends that you don't increase the hard limit beyond 1024 (the default) on Solaris 2.6 systems. Using Solaris as an application server -------------------------------------------------------------------------- Each emulator session requires one pseudo-tty. For example, 50 users running 10 applications each on one application server requires 500 pseudo-ttys. To set the number of pseudo-ttys, edit your /etc/system file (make a backup first) and add the following line: set pt_cnt= where is the number of pseudo-ttys you require. To create the new devices, reboot with the "-r" option. See http://sunsolve.sun.com/pub-cgi/retrieve.pl?type=0&doc=infodoc/21622 for advice on increasing pseudo-ttys. -------------------------------------------------------------------------- TurboLinux 6.0+ [511416] -------------------------------------------------------------------------- Tarantella requires that your system is configured to use shadow passwords, storing username and password information in /etc/shadow. Setup warns if your system doesn't use shadow passwords. IMPORTANT: On systems that don't use shadow passwords, users are unable to log in to Tarantella. To convert your system to use shadow passwords, use pwconv. See the pwconv(8) man page and the Linux Shadow Password HOWTO at http://www.linuxdoc.org/HOWTO/Shadow-Password-HOWTO.html, which gives a good overview of the issues you may encounter. -------------------------------------------------------------------------- UnixWare 7.1.1+ [513607] -------------------------------------------------------------------------- You should install the following patches (available from your support provider or from SCO Support Services, http://www.sco.com/support): set71101i UnixWare 7.1.1 Maintenance Set ftp://ftp.sco.com/Supplements/unixware7/ms71101 ptf7410h Thread lib patch ftp://ftp.sco.com/SLS/ptf7410h.Z ptf7666c TCP/IP supplement ftp://ftp.sco.com/SLS/ptf7666c.Z ptf7137a UnixWare 7.1.1 CDE Desktop Supplement (only required if you plan to run CDE Desktop on your Tarantella server) ftp://ftp.sco.com/SLS/ptf7137a.Z Newer patches may become available over time. Kernel tuning -------------------------------------------------------------------------- We recommend you use scoadmin to tune the kernel for optimal performance of Tarantella servers. Raise the following parameters to the specified values if they are currently less than the values shown: Device Drivers NUMREGPT 3072 NUMSCOPT 1024 Virtual Memory DRV_SEGKMEM_BYTES 0x147A000 File System RSTCHOWN 0 Security CONSOLE_SECURITY 0 Process Limits MAXUP 5000 MAXULWP 65000 NPROC 12500 SFNOLIM 2048 HFNOLIM 2048 Virtual Memory SEGKMEM_BYTES 0x2000000 Miscellaneous ARG_MAX 1048576 MAXLINK 32767 File System NBUF 128 NHBUF 32 IPC SEMMNI 10000 Tuning TCP/IP parameters -------------------------------------------------------------------------- You should also tune TCP/IP parameters. Run the following command as root: inconfig tcp_2msl 30 Set the following parameters in the relevant files in the /etc/conf/sdevice.d directory: tcp 4000 ticlts 1000 ticotsor 1000 ticots 8192 -------------------------------------------------------------------------- Additional kernel tuning for the Tarantella Mainframe Connectivity Pack -------------------------------------------------------------------------- The Tarantella Mainframe Connectivity Pack uses the third-party TN3270E product, which may require additional kernel tuning on your system. The information provided lists the the resources that TN3270E requires. To determine the actual values required for your system, you need to know the resource requirements of other applications running on the system. Kernel parameters required for supported operating systems -------------------------------------------------------------------------- Some operating systems only require some of the parameters to be tuned: HP-UX 10.20+ SHMMNI, SEMMNI, SEMMNS, SEMMNU IBM AIX 4.3+ No tuning required SCO OpenServer Release 5.0.5+ All five parameters SPARC Solaris 2.6+ All five parameters UnixWare 7+ SHMMNI, SEMMNI Definitions -------------------------------------------------------------------------- "TN3270E invocations" is the maximum number of TN3270E programs which will be running concurrently on the system. "HLLAPI sessions" is the total number of TN3270E sessions, for all of the TN3270E programs running with an HLLAPI session ID assigned. HLLAPI session IDs are assigned through the style file or with the -h option. Command line options -------------------------------------------------------------------------- -h allows a hexadecimal HLLAPI session ID to be specified for a TN3270E session. -b starts the TN3270E program as a background process. -e disables the menu interface. Formulas for TN3270E with neither the -b or -e command line options: SHMMNI = 1 + (TN3270E invocations) + (HLLAPI sessions) SEMMNI = (2 x TN3270E invocations) + (HLLAPI sessions) SEMMNS = (2 x TN3270E invocations) + (2 x HLLAPI sessions) SEMMAP = half the value of SEMMNS SEMMNU = (2 x TN3270E invocations) + (HLLAPI sessions) Formulas for TN3270E with the -b or -e command line option specified: SHMMNI = same as above SEMMNI = HLLAPI sessions SEMMNS = 2 x HLLAPI sessions SEMMAP = half the value of SEMMNS SEMMNU = HLLAPI sessions Additional kernel tuning for HLLAPI applications -------------------------------------------------------------------------- SHMSEG must be set on all operating systems except AIX when a single HLLAPI application must access multiple TN3270E sessions. SHMSEG = 1 + the maximum number of HLLAPI sessions to be accessed by a single HLLAPI application process. Shared memory sizes -------------------------------------------------------------------------- In most cases the shared memory sizes configured by default will be sufficient. For the few cases where this is not true, formulas are provided to calculate the approximate shared memory size required by TN3270E: - Without the -b option = (90K * TN3270E invocations) + (14K * HLLAPI sessions) - With th -b option = (19K * TN3270E invocations) + (14K * HLLAPI sessions) Process and socket requirements -------------------------------------------------------------------------- TN3270E uses two processes per invocation when run without either the -b or the -e options. Only one process is used with either the -b or -e option specified. This is true for both the Motif and character TN3270E versions. TN3270E uses one TCP socket per host session. -------------------------------------------------------------------------- Installing Tarantella -------------------------------------------------------------------------- 1 Log in as root on the host on which you want to install Tarantella. 2 Change to the directory where the Tarantella CD is mounted. 3 To install the Tarantella Base Component, type one of the following: sh ttaaxo1.shx Compaq Tru64 UNIX 4.0D+ sh ttapahp.shx HP-UX 10.20+ sh ttarsai.shx IBM AIX 4.3+ sh ttai3li.shx Caldera OpenLinux eServer 2.3+, Red Hat Linux 6.2+, SuSE Linux 6.3+, TurboLinux 6.0+ sh ttai3sc.shx SCO OpenServer Release 5.0.5+ sh ttaspso.shx SPARC Solaris 2.6+ sh ttai3un.shx UnixWare 7.1.1+ 4 Follow the instructions on your screen. 5 To install the Tarantella Mainframe Connectivity Pack software, type one of the following: sh mcp/mcppahp.shx HP-UX 10.20+ sh mcp/mcprsai.shx IBM AIX 4.3+ sh mcp/mcpi3sc.shx SCO OpenServer Release 5.0.5+ sh mcp/mcpspso.shx SPARC Solaris 2.6+ sh mcp/mcpi3un.shx UnixWare 7.1.1+ Note that this pack is not available for all systems. 6 To install the Tarantella AS/400 Connectivity Pack software, type one of the following: sh acp/acppahp.shx HP-UX 10.20+ sh acp/acprsai.shx IBM AIX 4.3+ sh acp/acpi3li.shx Caldera OpenLinux eServer 2.3+, Red Hat Linux 6.2+, SuSE Linux 6.3+, TurboLinux 6.0+ sh acp/acpi3sc.shx SCO OpenServer Release 5.0.5+ sh acp/acpspso.shx SPARC Solaris 2.6+ sh acp/acpi3un.shx UnixWare 7.1.1+ Note that this pack is not available for all systems. 7 To install the Tarantella Security Pack software, type one of the following: sh tsp/tspaxo1.shx Compaq Tru64 UNIX 4.0D+ sh tsp/tsppahp.shx HP-UX 10.20+ sh tsp/tsprsai.shx IBM AIX 4.3+ sh tsp/tspi3li.shx Caldera OpenLinux eServer 2.3+, Red Hat Linux 6.2+, SuSE Linux 6.3+, TurboLinux 6.0+ sh tsp/tspi3sc.shx SCO OpenServer Release 5.0.5+ sh tsp/tspspso.shx SPARC Solaris 2.6+ sh tsp/tspi3un.shx UnixWare 7.1.1+ IMPORTANT: Installing the Tarantella Security Pack does *not* enable SSL. For each host on which the Tarantella Security Pack is installed, a valid X.509 certificate is required before SSL connections are available. 8 To install any of the optional font packages, type the following: sh font/ttafandr.shx Andrew X fonts sh font/ttafhang.shx Hangul X fonts sh font/ttaficl.shx ICL X fonts sh font/ttaforie.shx Oriental X fonts sh font/ttafscot.shx SCO Term X fonts Installation notes -------------------------------------------------------------------------- - If you're creating a Tarantella array, we recommend that you install and check each server separately before creating the array. You should install the same set of optional packages on every server in the array. - If you're upgrading from an earlier version of Tarantella, you should restart the web server to ensure it sends the latest files to web browsers. All users of Tarantella should restart their web browsers before connecting to the upgraded server. - If you're installing Tarantella on a UnixWare system, remove unwanted files from /var/tmp before installing Tarantella. If you see an error message informing you that there isn't sufficient space in /var/tmp, type "umount /var/tmp" and try to install Tarantella again. - If you're installing Tarantella on an SCO OpenServer system, Setup appears to skip through a list of questions asked during the installation of a printer. This is correct: Setup supplies the answers automatically. [129306] -------------------------------------------------------------------------- Installing the Tarantella Native Client for Microsoft Windows -------------------------------------------------------------------------- 1 Copy the Native Client Setup program (tspwin32.exe) from the native directory on the CD to a temporary directory on your PC. 2 Browse to the temporary directory and double-click tspwin32.exe. -------------------------------------------------------------------------- Installing the Tarantella Native Client for UNIX/Linux -------------------------------------------------------------------------- 1 Copy one of the following Native Client tar files from the native directory on the CD to a temporary directory on your system: tncpahp.tar HP-UX 10.20+ tnci3li.tar Caldera OpenLinux eServer 2.3+, Red Hat Linux 6.2+, SuSE Linux 6.3+, TurboLinux 6.0+ tncspso.tar SPARC Solaris 2.6+ 2 At a command prompt, extract the tar file by typing tar xvf . 3 Install the Native Client by typing sh ttwebtop/install. -------------------------------------------------------------------------- Tarantella Enhancement Modules -------------------------------------------------------------------------- Tarantella Enhancement Modules provide support for some Tarantella features and are placed by Setup in the modules directory (var/docroot/modules) of the Tarantella server. To install a Tarantella Enhancement Module locally on an application server, download it from http:///tarantella/cgi-bin/modules.cgi. -------------------------------------------------------------------------- Configuring a web server for use with Tarantella -------------------------------------------------------------------------- Before you can use Tarantella, you must configure your web server in two ways: - Add a Document directory for the Tarantella document root. - Add a Program (CGI) directory for the cgi-bin subdirectory of the document root. How you do this depends on your web server. See your web server's documentation for full instructions, or read one of the following sections. IMPORTANT: If you're upgrading from Tarantella Enterprise II or earlier (version 1.x), you must reconfigure your web server. Apache web servers -------------------------------------------------------------------------- You must add two configuration directives to one of your web server configuration files (for example, httpd.conf): ScriptAlias /tarantella/cgi-bin /var/docroot/cgi-bin Alias /tarantella /var/docroot IMPORTANT: The lines must be in the order shown. Replace with the directory in which you installed Tarantella. Tarantella Setup displays what you must use as part of the "What you must do next" section. You should also ensure the web server follows symbolic links. The Directory directive for / should include "Options FollowSymLinks". These changes assume you are using the default configuration of Apache. See your web server documentation for more information. You must restart the web server for the configuration change to take effect. Netscape web servers -------------------------------------------------------------------------- 1 Start the Netscape Administration Server and connect to it using the Netscape server administrator's username and password. 2 Click the web server you want to use for Tarantella. 3 In the top frame, click Content Management. 4 In the left frame, click Additional Document Directories: - For URL Prefix, type "tarantella". - In Map To Directory, type "/var/docroot", replacing with the directory in which you installed Tarantella. (Tarantella Setup displays what you must use as part of the "What you must do next" section.) 5 Click OK, then click Save. 6 In the top frame, click Programs. 7 In the left frame, click CGI Directory: - For URL Prefix, type "tarantella/cgi-bin". - In Map To Directory, type the name of the cgi-bin subdirectory, "/var/docroot/cgi-bin", replacing with the directory in which you installed Tarantella. (Tarantella Setup displays what you must use as part of the "What you must do next" section.) 8 Click OK. 9, Click Save and Apply. Known web server problems -------------------------------------------------------------------------- Problem: Users can't download the Tarantella Native Client. [125591] Cause: By default, some Netscape web servers treat files with ".exe" extensions as CGI programs to run on the server, rather than files to download to the client. Solution: To allow users to download the Tarantella Native Client, you should ensure your web server is configured correctly. See http://help.netscape.com/kb/corporate/19960513-130.html (Setting your server to allow downloading of .EXE files) on Netscape's web site for instructions. You need to edit your web server's mime.types file, to remove "exe" as an extension for the "magnus-internal/cgi" type, and add it as an extension for the "application/octet-stream" type. -------------------------------------------------------------------------- Where to look for more information -------------------------------------------------------------------------- After installing Tarantella, Setup points you to the "Before you begin" section of the online documentation. This includes all the essential information to help you get started with Tarantella. Your Tarantella webtop contains links to detailed Help for users and Tarantella Administrators. You can also check http://www.tarantella.com/knowhow for up-to-date information on this version of Tarantella. For extensive online services (including FAQ, knowledge library and documentation) or to find out details of purchasable Support services, see the Tarantella Support and Services web site at http://www.tarantella.com/support. -------------------------------------------------------------------------- Copyright (C) 1997-2001 Tarantella, Inc., a wholly owned subsidiary and copyright assignee of The Santa Cruz Operation, Inc. All rights reserved. The names of companies referred to herein, their corporate logos, the names of their hardware and their software may be tradenames, trademarks or registered trademarks of their respective owners and manufacturers. $Id: README,v 1.52 2001/04/30 11:41:56 davidsm Exp $ --------------------------------------------------------------------------