| |
| META TOPICPARENT |
name="WmsxSoftware" |
WMSX |
| | Provider is the background process which does the actual work. There can be only one provider running on a machine per user. Start with: |
|
<
< | wmsx-provider.sh -v myworkdir |
>
> | wmsx-provider.sh myworkdir [-v] |
| |
where: |
|
<
< |
-
-v - Specifies that you want debug output on the console. Leave this out once you feel comfortable.
|
| |
-
myworkdir - Location of the working directory. This is where all the logging and output goes. You may want to set this to a location inside your home directory.
|
|
>
> |
-
-v - Specifies that you want debug output on the console. Leave this out once you feel comfortable.
|
| |
After the start of the provider, directories log, debug and out is prepared under the working directory. The logging informations of the WMSX actions are written into a file under the log directory. The files jobids.all, jobids.running, jobids.failed and jobids.done under the working directory contain the unique job identifiers of the sent Grid jobs. |
| | wmsx-requestor.sh -option
|
|
<
< | A complete list of options is available with -h. Some options are: |
>
> | A complete list of options is available with -h. Some options are: |
| |
-
-f - Check if the provider is running.
-
-k - Kill provider.
|
| | For each COMMAND in the ArgList file, there may be a JDL file COMMAND.jdl, to customize the properties of your job.
The structure of a WMSX JDL file is similar to traditional JDL files, however the supported variables are only: |
|
>
> |
-
JobType - If this variable is set to
"Interactive", the jobs will be run as interactively in the sense that the StdOut / StdError is retrieved on-the-fly, so you are able to see what your job is currently doing. If not set, the job is not interactive by default.
|
| |
-
Archive - Name of the program archive file. This is the name of the tarball, containing your program. If not specified, defaults to
"COMMAND.tar.gz". (Must be of tar-gz format!)
-
ProgramDir - Name of the root directory inside the program archive file. The files and directories of your program archive are assumed to be under this directory, and their paths are assumed to be given relative to this directory. Setting this to
"." means that the content of your tarball is not wrapped in a directory. If not specified, defaults to "COMMAND".
-
Executable - Name of the executable to run inside the
ProgramDir. If not specified, defaults to "COMMAND".
-
OutputDirectory - The name of the directory under
ProgramDir, where the output of your program is written. This is the directory, which is going to be retrieved by the framework as output. If not specified, defaults to "out".
|
|
<
< |
-
JobType - If this variable is set to
"Interactive", the jobs will be run as interactively in the sense that the StdOut / StdError is retrieved on-the-fly, so you are able to see what your job is currently doing. If not set, the job is not interactive by default.
|
| |
-
Software - List of software that must be present (executable) on the target machine. The special key
"AFS" requires and checks AFS presence. E.g.: Software = {"AFS", "g++"};. If not set, defaults to empty.
-
Requirements - Extra queue requirements, like in a traditional JDL file. If not set, defaults to empty.
|
