lslib
Application Programming Interface (API) library routines for LSF servicesLSLIB routines allow application programs to contact the Load Information Manager (LIM) and Remote Execution Server (RES) daemons in order to obtain LSF services. These services include obtaining static system configuration information and dynamic load information for the hosts in distributed clusters, obtaining task placement advice from LIM, executing tasks (UNIX processes) on remote hosts with a high degree of transparency using RES, remote file operations across hosts that do not share file systems, performing remote terminal I/O and signal operations, and other related functions. You can build distributed applications on top of LSLIB to effectively exploit the resources available on the network, improving application performance and resource accessibility.
- Library routines for obtaining load sharing cluster configuration information.
- Library routines for obtaining host configuration information.
- Library routines for obtaining host load information. An application can use this information to make task placement decisions instead of using LIM's.
- Library routines implementing LIM's task placement policy. These routines include calls to obtain task placement information, and calls to adjust host load measures.
- Library routines for displaying and manipulating the local and remote task lists. These lists specify the eligibility of various types of tasks for remote execution, and their resource requirement characteristics.
- REMOTE EXECUTION
- Library routines related to remote execution, including initiation, connection and remote environment manipulation.
- Library routines for establishing and querying remote connections.
- Library routines for executing remote tasks.
- Library routines for querying and manipulating stdin for remote tasks.
- Wait for a remote or local task, then return its status.
- Library routines for operations on files on remote hosts.
- Library routines for administering and controlling the LSF system.
- Note:
- All LSLIB routines require that the LSF header file <lsf/lsf.h> be included.
- Many LSLIB APIs return a pointer to an array or structure. These data structures are in static storage or on the heap. The next time the routine is called, the storage is overwritten or freed.
- Any program using LSLIB routines that change the state of the LSF system must be setuid to root if LSF_AUTH is not defined in the lsf.conf file.
- Any program using LSLIB routines for remote execution services or for operations on files on remote hosts must call ls_initrex() before calling any of the other routines.
- On systems which have both System V and BSD programming interfaces, LSLIB typically requires the BSD programming interface. On System V-based versions of UNIX, for example SGI IRIX, it is normally necessary to link applications using LSLIB with the BSD compatibility library.
- On AFS systems, the following needs to be added to the end of your linkage specifications when linking with LSLIB (assuming your AFS library path is /usr/afsws):
- For HP-UX and Solaris,
- -lc -L/usr/afsws/lib -L/usr/afsws/lib/afs -lsys -lrx -llwp /usr/afsws/lib/afs/util.a
- For other platforms,
Files:
- -lc -L/usr/afsws/lib -L/usr/afsws/lib/afs -lsys -lrx -llwp
- ${LSF_ENVDIR:-/etc}/lsf.conf
$LSF_CONFDIR/lsf.shared
$LSF_CONFDIR/lsf.cluster.cluster_name
$LSF_CONFDIR/lsf.task
$LSF_CONFDIR/lsf.task.cluster_name
- See also:
- ls_chdir
Date Modified: 16 Jul 2014
Terms of Use
Copyright © 1994-2014 International Business Machines Corp.
US Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.