Upgrading Platform LSF on UNIX and Linux

Transcription

1 Upgrading Platform LSF on UNIX and Linux Contents Upgrade your LSF Cluster on page 2 Compatibility Notes on page 4 Get Technical Support on page 15 Version 6.2 February Platform Computing Comments to: doc@platform.com

2 Upgrade your LSF Cluster Upgrade your LSF Cluster Contents Get ready to upgrade Download LSF distribution tar files Use lsfinstall to upgrade LSF Use hostsetup to set up LSF hosts Restart your cluster Get ready to upgrade 1 Inactivate all queues to make sure that no new jobs will be dispatched during the upgrade. After upgrading, remember to activate the queues again so pending jobs can be dispatched. To inactivate all LSF queues, use the following command: % badmin qinact all To reactivate all LSF queues after upgrading, use the following command: % badmin qact all 2 Back up your existing LSF_CONFDIR, LSB_CONFDIR, and LSB_SHAREDIR according to the procedures at your site. 3 Get an LSF Version 6.2 license and create a license file (license.dat). Download LSF distribution tar files 1 Log on to the LSF file server host as root. 2 FTP to ftp.platform.com and get the following files from the /distrib/6.2/platform_lsf/ directory on ftp.platform.com: IMPORTANT LSF installation script tar file lsf6.2_lsfinstall.tar.z LSF distribution tar files for all host types you need Put the distribution tar files in the same directory as lsf6.2_lsfinstall.tar.z. Download and read LSF Version 6.2 release_notes.html for detailed steps for downloading LSF distribution tar files. 3 Uncompress and extract lsf6.2_lsfinstall.tar.z: # zcat lsf6.2_lsfinstall.tar.z tar xvf - DO NOT extract the distribution tar files. Use lsfinstall to upgrade LSF 1 Change to lsf6.2_lsfinstall/. 2 Read lsf6.2_lsfinstall/install.config and decide which installation variables you need to set. 3 Edit lsf6.2_lsfinstall/install.config to set the installation variables you need. 4 Follow the instructions in lsf_unix_install_6.2.pdf to run: #./lsfinstall -f install.config 2 Upgrading Platform LSF on UNIX and Linux

3 Upgrading Platform LSF on UNIX and Linux IMPORTANT You must run lsfinstall as root. lsfinstall backs up the following configuration files for your current installation in LSF_CONFDIR: cshrc.lsf lsf.cluster.cluster_name lsf.conf lsf.shared profile.lsf Use hostsetup to set up LSF hosts 1 Follow the steps in lsf6.2_lsfinstall/lsf_getting_started.html to set up your LSF hosts (hostsetup). a Log on to each LSF server host as root. Start with the LSF master host. b Run hostsetup on each LSF server host. For example: # cd /usr/share/lsf/6.2/install #./hostsetup --top="/usr/share/lsf/" For complete hostsetup usage, enter hostsetup -h. 2 Set your LSF environment: For csh or tcsh: % source LSF_TOP/conf/cshrc.lsf For sh, ksh, or bash: $. LSF_TOP/conf/profile.lsf 3 Follow the steps in lsf6.2_lsfinstall/lsf_quick_admin.html to update your license. Restart your cluster 1 Use the following commands to shut down the old LSF daemons: % badmin hshutdown all % lsadmin resshutdown all % lsadmin limshutdown all 2 Use the following commands to restart LSF using the new 6.2 daemons: % lsadmin limstartup all % lsadmin resstartup all % badmin hstartup all 3 Follow the steps in lsf6.2_lsfinstall/lsf_quick_admin.html to verify that your upgraded cluster is operating correctly. 4 Use the following command to reactivate all LSF queues after upgrading: % badmin qact all 5 Have users run one of the LSF shell environment files to switch their LSF environment to the new cluster. Follow the steps in lsf6.2_lsfinstall/lsf_quick_admin.html for using LSF_CONFDIR/cshrc.lsf and LSF_CONFDIR/profile.lsf to set up the LSF environment for users. After the new cluster is up and running, users can start submitting jobs to it. Upgrading Platform LSF on UNIX and Linux 3

4 Compatibility Notes Compatibility Notes Contents Maintenance pack availability on page 4 API compatibility on page 4 Server host compatibility Platform LSF on page 5 Cross-product compatibility on page 5 System requirements on page 5 New 64-bit Linux host types on page 5 Changed behavior on page 6 New configuration parameters and environment variables on page 7 New command options and output on page 11 New files added to installation on page 14 Maintenance pack availability API compatibility At release, Platform LSF Version 6.2 includes all bug fixes and solutions up to and including the August 2005 Platform LSF Version 6.1 Maintenance Pack. Fixes after August 2005 will be included in the first Platform LSF Version 6.2 Maintenance Pack. Full backward compatibility: your applications will run under LSF Version 6.2 without changing any code. The Platform LSF Version 6.2 API is fully compatible with the LSF Version 6.x. and 5.x APIs. An application linked with the LSF Version 6.x or 5.x libraries will run under LSF Version 6.2 without relinking. To take full advantage of new Platform LSF Version 6.2 features, you should recompile your existing LSF applications with LSF Version 6.2. New LSF APIs The following new APIs have been added for LSF Version 6.2: lsb_addreservation() lsb_geteventrecbyline() lsb_hostinfo_cond() lsb_killbulkjobs() lsb_openjobinfo_a_ext() lsb_readjobinfo_cond() lsb_removereservation() lsb_reservationinfo() New LSF License Scheduler APIs The following new APIs have been added for LSF License Scheduler Version 6.2: glb_close_all() glb_groupinfolist() glb_info() glb_init_all() glb_jobinfo() glb_param() 4 Upgrading Platform LSF on UNIX and Linux

5 Upgrading Platform LSF on UNIX and Linux glb_perror() glb_userinfo() glb_workloadinfo() Server host compatibility Platform LSF Cross-product compatibility System requirements To use new features introduced in Platform LSF Version 6.2, you must upgrade all hosts in your cluster to 6.2. LSF 6.x and 5.x servers are compatible with Version 6.2 master hosts. All LSF 6.x and 5.x features are supported by 6.2 master hosts. New 64-bit Linux host types See Platform LSF Family of Products Compatibility at for more information. See the Platform Computing Web site for information about supported operating systems and system requirements for the Platform LSF family of products: Platform LSF and Platform LSF HPC Platform LSF License Scheduler The pre-6.2 LINUX64 host type is ambiguous. LSF reports the same LINUX64 host type for hosts that are not binary compatible (for example, AMD64 and Intel IA-64 Linux hosts). Jobs requesting the LINUX64 host type can get dispatched to hosts where the job cannot run. The LINUX64 host type has been replaced with two new host types to ensure jobs are dispatched to the correct host type: X86_64 for AMD64 and EM64T Linux hosts IA64 for Intel IA-64 Linux hosts Issue After upgrading the cluster, existing jobs that require the obsolete LINUX64 host type cannot run. Solution: Wait for all jobs to finish before upgrading, or use bmod to change the host type from LINUX64 to one of the new host types to allow jobs to run on the hosts of the correct type. Issue In LSF MultiCluster, jobs submitted from an LSF 6.1 cluster requiring hosts of type LINUX64 do not run on an LSF 6.2 cluster because no hosts of that type exist in the execution cluster. Solution: On the submission cluster: a b Manually add the new X86_64 and IA64 host types to lsf.shared. Submit the jobs again, or use bmod to change the host type from LINUX64 to one of the new host types to allow jobs to run on the hosts of the correct type. Upgrading Platform LSF on UNIX and Linux 5

6 Compatibility Notes Changed behavior Open advance reservations Open advance reservations allow jobs to run even after the associated reservation expires. A job with the open advance reservation will only be treated as an advance reservation job during the reservation window, after which it becomes a normal job. This prevents the job from being killed and ensures that LSF does not prevent any previously suspended jobs from running or interfere with any existing scheduling policies. Enforcement of dual-core CPU licenses on Linux Dual-core CPU hosts running Linux must be licensed by the lsf_dualcore_x86 license feature. Each dual core processor requires one standard LSF license and one lsf_dualcore_x86 license. Use lshosts -l to see the number of dual-core licenses enabled and needed. Enforcement of grid license managment plugin licenses The new license optimization features enabled by the grid license management plugin require the lsf_mv_grid_filter license feature. The number of lsf_mv_grid_filter licenses should be at least the number of LSF License Scheduler licenses. Banded licensing You can use permanent licenses with restictions in operating system and hardware configurations. These banded licenses have three classes, with the E-class licenses having no restrictions. Banded licenses support the following operating systems and hardware configurations: License type Supported operating systems Supported hardware B-Class Linux and Windows X86/AMD64/EM64T Up to two CPUs and 4 GB physical memory on a node S-Class Linux and Windows X86/AMD64/EM64T Up to four CPUs and 8 GB physical memory on a node Itanium2 Up to two CPUs and 4 GB physical memory on a node E-Class All LSF-supported operating systems All hardware Unlimited CPUs and physical memory on a node 6 Upgrading Platform LSF on UNIX and Linux

7 Upgrading Platform LSF on UNIX and Linux New configuration parameters and environment variables The following new parameters and environment variables have been added for LSF Version 6.2: lsb.hosts Condensed host groups To define condensed host groups, add a CONDENSE column to the HostGroup section. Under this column, enter Y to define a condensed host group or N to define an uncondensed host group, as shown in the following: Begin HostGroup GROUP_NAME CONDENSE GROUP_MEMBER groupa Y (hosta hostb hostd) groupb N (hostc hoste) End HostGroup Wildcards and special characters to define host names You can use special characters when defining host group members under the GROUP_MEMBER column to specify hosts. These are useful to define several hosts in a single entry, such as for a range of hosts, or for all host names with a certain text string. If a host matches more than one host group, that host is a member of all groups. If any host group is a condensed host group, the status and other details of the hosts are counted towards all of the matching host groups. When defining host group members, you can use string literals and the following special characters: Use a tilde (~) to exclude specified hosts or host groups from the list. The following example matches all hosts in the cluster except for hosta, hostb, and all members of the groupa host group:... (all ~hosta ~hostb ~groupa) The tilde can be used in conjunction with the other special characters below. Use an asterisk (*) as a wildcard character to represent any number of characters. The following example matches all hosts beginning with the text string hostc (such as hostca, hostc1, or hostcz1):... (hostc*) Use square brackets with a hyphen ([integer1 - integer2]) to define a range of non-negative integers at the end of a host name. The first integer must be less than the second integer. The following example matches all hosts from hostd51 to hostd100:... (hostd[51-100]) Use square brackets with commas ([integer1, integer2...]) to define individual non-negative integers at the end of a host name. The following example matches hostd101, hostd123, and hostd321:... (hostd[101,123,321]) Upgrading Platform LSF on UNIX and Linux 7

8 Compatibility Notes Use square brackets with commas and hyphens (such as [integer1 - integer2, integer3, integer4 - integer5]) to define different ranges of non-negative integers at the end of a host name. The following example matches all hosts from hostd1 to hostd100, hostd102, all hosts from hostd201 to hostd300, and hostd320):... (hostd[1-100,102, ,320]) Restrictions You cannot use more than one set of square brackets in a single host group definition. The following example is not correct:... (hosta[1-10]b[1-20] hostc[ ]) The following example is correct:... (hosta[1-20] hostc[ ]) You cannot define subgroups that contain wildcards and special characters. The following definition for groupb is not correct because groupa defines hosts with a wildcard: Begin HostGroup GROUP_NAME GROUP_MEMBER groupa (hosta*) groupb (groupa) End HostGroup lsb.params MAX_INFO_DIRS=num_subdirs Where num_subdirs specifies the number of subdirectories that you want to create under the LSF_SHAREDIR/cluster_name/logdir/info directory. Valid values are positive integers between 1 and The default value is 0. If your cluster has a lot of jobs resulting in a large info directory, you can tune your cluster by enabling LSF to create subdirectories in the info directory. Use MAX_INFO_DIRS in lsb.params to create the subdirectories and enable mbatchd to distribute the job files evenly throughout the subdirectories. For example: MAX_INFO_DIRS=10 mbatchd creates ten subdirectories from LSB_SHAREDIR/cluster_name/logdir/info/0 to LSB_SHAREDIR/cluster_name/logdir/info/9 Run badmin reconfig to create and use the subdirectories. If you enabled duplicate event logging, run badmin mbdrestart instead to restart mbatchd. If you specify MAX_INFO_DIRS after upgrading and decide to roll back the upgrade, pending jobs cannot be dispatched after downgrading to the previous release. You must kill the pending jobs and resubmit them. 8 Upgrading Platform LSF on UNIX and Linux

9 Upgrading Platform LSF on UNIX and Linux lsb.queues USERS=all [~user_name...] [~user_group...] [user_name...] [user_group... [~user_group...]] Use the not operator (~) to exclude users from the the all specification or from user groups. This is useful if you have a large number of users but only want to exclude a few users or groups from the queue definition. The not operator can only be used with the all keyword or to exclude users from user groups. The not operator does not exclude LSF administrators from the queue definintion. lsf.conf LSB_MAX_PROBE_SBD=integer Specifies the maximum number of sbatchd instances can be polled by mbatchd in the interval MBD_SLEEP_TIME/10. Use this parameter in large clusters to reduce the time it takes for mbatchd to probe all sbatchds. LSB_DISABLE_RERUN_POST_EXEC=y Y If set, and the job is rerunnable, the POST_EXEC configured in the queue is not executed if the job is rerun. Running of post-execution commands upon restart of a rerunanble job may not always be desirable. For example, if the post-exec removes certain files, or does other cleanup that should only happen if the job finishes successfully, use LSB_DISABLE_RERUN_POST_EXEC to prevent the post-exec from running and allow the succesful continuation of the job when it reruns. LSF_ENABLE_DUALCORE=Y N Enables job scheduling based on dual-core CPU information for a host. If yes (Y), LSF scheduling policies use the detected number of CPU cores as the number of physical CPUs on the host instead of the number of physical CPUs for job scheduling. For a dual-core host, lshosts shows the number of cores under ncpus instead of physical CPUs. To make use of dual-core CPUs for scheduling, hosts must have the lsf_dualcore_x86 license feature enabled. Each dual core processor requires one standard LSF license and one lsf_dualcore_x86 license. Use lshosts -l to see the number of dual-core licenses enabled and needed. LSF_LICENSE_ACCT_PATH=dir Specifies the location for the license accounting files. These include the license accounting files for LSF Family products. Use this parameter to define the location of all the license accounting files. By defining this parameter, you can store the license accounting files for the LSF Family of products in the same directory for convenience. LSF_LICENSE_NOTIFICATION_INTERVAL=hours Specifies how often notification is sent to the primary cluster administrator about overuse of LSF Family product licenses and License Scheduler tokens. The default is 24 hours. LSF_SHIFT_JIS_INPUT=y n Upgrading Platform LSF on UNIX and Linux 9

10 Compatibility Notes lsf.licensescheduler Enables LSF to accept Shift-JIS character encoding for job information (for example, user names, queue names, job names, job group names, project names, commands and arguments, esub parameters, external messages, etc.) MC_PLUGIN_REMOTE_RESOURCE=y MultiCluster job forwarding model only. By default, the submission cluster does not consider remote resources. Define MC_PLUGIN_REMOTE_RESOURCE=y in the submission cluster to allow consideration of remote resources. Parameters section: DISTRIBUTION_POLICY_VIOLATION_ACTION=(PERIOD reporting_period CMD reporting_command) Optional. Defines how License Scheduler handles distribution policy violations. Distribution policy violations are caused by non-lsf workloads because LSF License Scheduler explicitly follows its distribution policies. EXT_FILTER_PORT=integer Defines the TCP listening port used by all external plugins to communicate with License Scheduler hosts. Specify any non-privileged port number. LS_MAX_TASKMAN_SESSIONS=integer Defines the maximum number of taskman jobs that run simultaneously. This prevents system-wide performance issues that occur if there are a large number of taskman jobs running in License Scheduler. ServiceDomain section LIC_FLEX_API_ENABLE=y n Enables the Macrovision FLEXnet APIs to replace the default behaviour of scheduling based on lmstat data. You must also configure License Scheduler and your vendor daemons to work with the Macrovision FLEXnet Manager package. Feature section GROUP_DISTRIBUTION=top_level_hierarchy_name Required if DISTRIBUTION is not defined. Defines the name of the hierarchical group containing the distribution policy attached to this feature. GROUP_DISTRIBUTION and DISTRIBUTION are mutually exclusive. If they are both defined in the same feature, the License Scheduler daemon returns an error and ignores this feature. SERVICE_DOMAINS=service_domain_name... Required if GROUP_DISTRIBUTION is defined. Specifies the service domains that provide tokens for this feature. WORKLOAD_DISTRIBUTION=[service_domain_name(LSF lsf_distribuion[/enforced_distribution] NON_LSF non_lsf_distribution)]... Optional. Defines the distribution given to each LSF and non-lsf workload within the specified service domain. ProjectGroup section 10 Upgrading Platform LSF on UNIX and Linux

11 Upgrading Platform LSF on UNIX and Linux Environment variables New section defines the hierarchical relationships of projects. Define shared and non-shared projects, limits, and ownership among groups of LSF License Scheduler projects. Projects section PRIORITY Optional. Defines the priority for each project where 0 is the lowest priority, and the higher number specifies a higher priority. This column allows the user to override the default behaviour, which is to look at the cumulative inuse to determine the preemption order (the project using the most license tokens is preempted first). CLEARCASE_DRIVE=drive_letter: CLEARCASE_MOUNTDIR=path LS_LICENSE_SERVER_feature="domain:server:num_available..." New command options and output Condensed host groups bacct bkill The following command options and output have changed for LSF Version 6.2: Condensed host groups defined by CONDENSE in the HostGroup section of lsb.hosts display condensed information for the following commands: bhosts and bhosts -w bhosts displays condensed output for condensed host groups. These host groups are displayed as a single entry with the name as defined by GROUP_NAME in the HostGroup section of lsb.hosts. bhosts -l and bhosts -X display uncondensed output. bjobs and bjobs -w bjobs displays condensed output for condensed host groups. These host groups are displayed as a single entry with the name as defined by GROUP_NAME in the HostGroup section of lsb.hosts. If you defined LSB_SHORT_HOSTLIST=1 in lsf.conf, parallel jobs running in the same condensed host group are displayed as an abbreviated list. bjobs -l and bjobs -X display uncondensed output. bacct does not show local pending batch jobs killed using bkill -b. bacct shows MultiCluster jobs and local running jobs even if they are killed using bkill -b. bkill -b kills large numbers of jobs as soon as possible. Use bkill -b to kill a large number of jobs faster than with normal means. Local pending jobs are killed immediately and cleaned up as soon as possible, ignoring the time interval specified by CLEAN_PERIOD in lsb.params. Jobs killed in this manner are not logged to lsb.acct. Other jobs, such as running jobs, are killed as soon as possible and cleaned up normally. If the -b option is used with the 0 subcommand, bkill kills all applicable jobs and silently skips the jobs that cannot be killed. The -b option is ignored if used with the -r or -s options. Upgrading Platform LSF on UNIX and Linux 11

12 Compatibility Notes blinfo blinfo -G lists the hierarchical License Scheduler configuration information. If PRIORITY is defined in the Projects Section of lsf.licensescheduler, blinfo -Lp also lists the priorities of each project. bltasks bltasks -Lp displays information about tasks associated with the specified License Scheduler projects. blstat -G Displays dynamic hierarchical license information. bmgroup bmod blstat -G also works with the -t option to only display hierarchical information for the specified feature names. -s Displays license usage of the LSF and non-lsf workloads. Workload distributions are defined by WORKLOAD_DISTRIBUTION in lsf.licensescheduler. If there are any distribution policy violations, blstat marks these with an asterisk (*) at the beginning of the line. -S Displays information on the license server associated with license features. bmgroup -l identifies condensed host groups. These host groups are defined by CONDENSE in the HostGroup section of lsb.hosts. LSF users can modify the termination time of their open advance reservations without interfering with current job scheduling policies. For example, you specify two open advance reservations as follows: % brsvadd -o -n 1 -m hosta -u user1 -b 15:10 -e 15:30 Reservation user1#17 is created % brsvadd -o -n 1 -m hosta -u user1 -b 15:35 -e 15:50 Reservation user1#18 is created At 15:15, while job 122 in user1#17 is running, you modify its termination time as follows: % bmod -t 15: This termination time overlaps the reservation window of user1#18, in which job 245 started at 15:35. After modifying the termination time of job 122, the following events occur: At this time... These events occur... 15:35 Job 122 in reservation user1#17 suspends Job 245 in reservation user1#18 starts 15:40 Job 122 in reservation user#17 is still suspended Job 245 in reservation user#18 continues to run 15:50 Job 122 in reservation user1#17 suspends Job 245 in reservation user1#18 suspends 15:51 Job 122 in reservation user1#17 runs Job 245 in reservation user1#18 suspends At 15:50, both Job 122 in reservation user#17 and Job 245 in reservation user#18 are suspended. At this point, the existing scheduling policies determine which job runs; in this example, Job 122 in reservation user#17 runs. 12 Upgrading Platform LSF on UNIX and Linux

13 Upgrading Platform LSF on UNIX and Linux bparams bparams -l displays the value of the MAX_INFO_DIRS parameter brsvadd -o -o Creates an open advance reservation. A job with an open advance reservation will only have the advance reservation property during the reservation window, after which the job becomes a normal job, not subject to termination when the reservation window closes. You must specify the same information as for normal advance reservations. This prevents jobs from being killed if the reservation window is too small. Instead, the job is suspended and normal scheduling policies apply after the reservation window. -n If you also specify the reservation for system use with the -s option, -n is optional. brsvdel -s When specifying a system reservation with -s, you do not need to specify the number of processors to reserve with the -n option. You can delete multiple reservations at a time. brsvs -l Shows each advance reservation in multiline long format. The rows that follow the reservation information show the type of reservation (open or closed) and the status of any job associated with the specified reservation (EXIT, PEND, RUN, or SUSP). brun -w Displays reservation information in wide format without truncating fields. With brun -m "host_name[#num_cpus]... ", you can optionally specify the number of CPUs required per host for multihost parallel jobs. num_cpus distributes job slots according the number of CPUs on the host. If num_cpus is not defined, or if num_cpus is greater than the number of static CPUs on the host (or the number of free CPUs if -c is specified), LSF distributes job slots according to the number of static CPUs on the host, or the number of free CPUs on the host if -c is specified. bsub bsub supports commands to 512 characters long -J bsub -J supports job names up to 512 characters long -g bsub -g supports job group names of up to 512 characters long lshosts lshosts -l displays host information in a long multi-line format. In addition to the default fields, displays information about the maximum /tmp space, the number of local disks, the execution priority for remote jobs, load thresholds, run windows, and the license classes used or needed. If LSF_ENABLE_DUALCORE=Y in lsf.conf for dual-core CPU hosts lshosts displays the number of cores under the ncpus column instead of physical CPUs lshosts -l displays the number of dual-core licenses enabled and needed. Upgrading Platform LSF on UNIX and Linux 13

14 Compatibility Notes New files added to installation Platform LSF Platform LSF License Scheduler Symbolic links to LSF files The following new files have been added to the Platform LSF installation: win_install.config Contains options for Platform LSF for Windows installation and configuration using the silent install option. Use setup /I:win_install.config to install LSF using the options specified in win_install.config. The following components have been added to the Platform LSF HPC installation for LSF MVAPICH MPI integration and the LSF Intel MPI integration: esub.mvapich sets the mode: rsh, ssh, or mpd mvapich_wrapper esub.intelmpi intelmpi_wrapper The following new files have been added to the Platform LSF License Scheduler installation: LSF_BINDIR/blkill Terminates a running or waiting interactive task in License Scheduler. Users can kill their own tasks. You must be a License Scheduler administrator to terminate another user s task. LSF_BINDIR/bltasks Displays current information about interactive tasks managed by License Scheduler (submitted using taskman). By default, displays information about all tasks. LSF_BINDIR/taskman Checks out a license token and manages interactive UNIX applications LSF_LOGDIR/bld.license.acct The license and accounting file for LSF License Scheduler. LSF_LOGDIR/lsf.cluster_name.license.acct The license accounting file for LSF. There is one for each cluster, called lsf.cluster_name.license.acct, where cluster_name is the name of the cluster defined in the Cluster section of lsf.shared. setup.config Contains options for Platform LSF License Scheduler installation and configuration for systems without Platform LSF. You only need to edit this file if you are installing License Scheduler as a standalone product without LSF. If your installation uses symbolic links to other files in these directories, you must manually create links to these new files. 14 Upgrading Platform LSF on UNIX and Linux

15 Upgrading Platform LSF on UNIX and Linux Get Technical Support Contact Platform World Wide Web Mail Contact Platform Computing or your LSF vendor for technical support. Use one of the following to contact Platform technical support: Platform Support Platform Computing Corporation th Avenue Markham, Ontario Canada L3R 3T7 When contacting Platform, please include the full name of your company. See the Platform Web site at for other contact information. Get patch updates and other notifications We d like to hear from you Mail To get periodic patch update information, critical bug notification, and general support notification from Platform Support, contact supportnotice-request@platform.com with the subject line containing the word "subscribe". To get security related issue notification from Platform Support, contact securenotice-request@platform.com with the subject line containing the word "subscribe". If you find an error in any Platform documentation, or you have a suggestion for improving it, please let us know: doc@platform.com Information Development Platform Computing th Avenue Markham, Ontario Canada L3R 3T7 Be sure to tell us: The title of the manual you are commenting on The version of the product you are using The format of the manual (HTML or PDF) Upgrading Platform LSF on UNIX and Linux 15

16 Copyright Copyright Platform Computing Corporation All rights reserved. Although the information in this document has been carefully reviewed, Platform Computing Corporation ( Platform ) does not warrant it to be free of errors or omissions. Platform reserves the right to make corrections, updates, revisions or changes to the information in this document. UNLESS OTHERWISE EXPRESSLY STATED BY PLATFORM, THE PROGRAM DESCRIBED IN THIS DOCUMENT IS PROVIDED AS IS AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL PLATFORM COMPUTING BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, DATA, OR SAVINGS, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS PROGRAM. Document redistribution policy This document is protected by copyright and you may not redistribute or translate it into another language, in part or in whole. Internal redistribution You may only redistribute this document internally within your organization (for example, on an intranet) provided that you continue to check the Platform Web site for updates and update your version of the documentation. You may not make it available to your organization over the Internet. Trademarks LSF is a registered trademark of Platform Computing Corporation in the United States and in other jurisdictions. ACCELERATING INTELLIGENCE, PLATFORM COMPUTING, PLATFORM SYMPHONY, PLATFORM JOBSCHEDULER, and the PLATFORM and PLATFORM LSF logos are trademarks of Platform Computing Corporation in the United States and in other jurisdictions. UNIX is a registered trademark of The Open Group in the United States and in other jurisdictions. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Macrovision, Globetrotter, FLEXlm, FLEXnet, FLEXnet Manager, FLEXnet Connector, are registered trademarks or trademarks of Macrovision Corporation in the United States of America and/or other countries. 16 Upgrading Platform LSF on UNIX and Linux

17 Upgrading Platform LSF on UNIX and Linux Other products or services mentioned in this document are identified by the trademarks or service marks of their respective owners. Third Party License Agreements Third Party Copyright Notices Upgrading Platform LSF on UNIX and Linux 17

18 Copyright 18 Upgrading Platform LSF on UNIX and Linux