rploadgo man page on YellowDog

Man page or keyword search:  
man Server   18644 pages
apropos Keyword Search (all sections)
Output format
YellowDog logo
[printable version]

RPLOADGO(2)		      LAM REMOTE LIBRARY		   RPLOADGO(2)

NAME
       rploadgo - Load and execute a LAM program on a remote node.

C SYNOPSIS
       #include <kio.h>

       int  rploadgo  (int  srcnode,  int destnode, char *filename, int flags,
	      char **argv, int *pid, int *idx);

FORTRAN SYNOPSIS
       subroutine RPLDGO (srcnode, destnode, filename, flags, pid, idx, ierr)
integer srcnode, destnode, flags, pid, idx, ierr
character filename*(*)

ARGUMENTS
       srcnode	   where program is stored

       destnode	   where new process will be created

       filename	   program file

       flags	   runtime flags passed to new process

       argv	   null-terminated array of strings to be passed  as  command-
		   line arguments to the new process

       pid	   new process identifier (output)

       idx	   new process index (output)

DESCRIPTION
       If  the	source and destination nodes are identical, the program is not
       transferred and the process is created with rpcreate(2).	 Otherwise the
       program is transferred with rload(2), stored in /tmp on the destination
       node, and created with rpgo(2).

       If the source node is the local node, the program is located by search‐
       ing  the	 directories  defined  in the PATH environment variable of the
       caller.	Otherwise, the PATH variable of the remote LAM daemon is used.
       Usually,	 the  only difference is in how the "." directory is resolved.
       On the local node it is the current working directory  of  the  calling
       process.	 On a remote node it is the user's home directory.

   Current Working Directory
       By  default,  rploadgo()	 will  propagate  the caller's current working
       directory to the created process if target  node	 is  the  local	 node.
       This  is accomplished by passing the RTF_CWD runtime flag to rpgo(2) or
       rpcreate(2).  A remote process will assume the remote home directory as
       its  current  working  directory.  This behaviour can be changed by the
       RTF_APPWD runtime flag.

   Runtime Flags
       Runtimes flags are defined in <kio.h> (<NET.h> for Fortran) and can  be
       added together in any combination.

       RTF_WAIT	   The new process will send a message to the calling process,
		   received by rpwait(2), when it exits.  This flag is used if
		   the	parent	is  interested	in  the exit code of the child
		   process.  Failure to call rpwait(2)	at  some  point	 after
		   using this flag will leave stray messages with weird events
		   in buffers on the caller's node.

       RTF_TRACE   Enable tracing for the new process.

       RTF_APPWD   The current working directory will be the location  of  the
		   executable program.

ERRORS
       ENOPDESCRIPTORS	   The remote process descriptor table is full.

       ENOFLDESCRIPTORS	   The table of strorage blocks (kept by the flat dae‐
			   mon) is full.

SEE ALSO
       rpcreate(2), rpgo(2), rpwait(2)

LAM 7.1.2			  March, 2006			   RPLOADGO(2)
[top]

List of man pages available for YellowDog

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net