1GLOBUS-FORK-STARTE(8)    Grid Community Toolkit Manual   GLOBUS-FORK-STARTE(8)
2
3
4

NAME

6       globus-fork-starter - Start and monitor a fork job
7

SYNOPSIS

9       globus-fork-starter
10

DESCRIPTION

12       The globus-fork-starter program is executes jobs specified on its
13       standard input stream, recording the job state changes to a file
14       defined in the /etc/globus-fork.conf configuration file. It runs until
15       its standard input stream is closed and all jobs it is managing have
16       terminated. The log generated by this program can be used by the SEG to
17       provide job state changes and exit codes to the GRAM service. The
18       globus-fork-starter program is typically started by the fork GRAM
19       module.
20
21       The globus-fork-starter program expects its input to be a series of
22       task definitions, separated by the newline character, each representing
23       a separate job. Each task definition contains a number of fields,
24       separated by the colon character. The first field is always the literal
25       string 100 indicating the message format, the second field is a unique
26       job tag that will be distinguish the reply from this program when
27       multiple jobs are submitted. The rest of fields contain attribute
28       bindings. The supported attributes are:
29
30       directory
31           Working directory of the job
32
33       environment
34           Comma-separated list of strings defining environment variables. The
35           form of these strings is var=value.
36
37       count
38           Number of processes to start.
39
40       executable
41           Full path to the executable to run.
42
43       arguments
44           Comma-separated list of command-line arguments for the job
45
46       stdin
47           Full path to a file containing the input of the job.
48
49       stdout
50           Full path to a file to write the output of the job to.
51
52       stderr
53           Full path to a file to write the error stream of the job.
54
55       Within each field, the following characters may be escaped by preceding
56       them with the backslash character: - backslash (\) - semicolor (;) -
57       comma (,) - equal (=)
58
59       Additionally, newline can be represented within a field by using the
60       escape sequence \n.
61
62       For each job the globus-fork-starter processes, it replies by writing a
63       single line to standard output. The replies again consist of a number
64       of fields separated by the semicolon character.
65
66       For a successful job start, the first field of the reply is the literal
67       101, the second field is the tag from the input, and the third field is
68       a comma-separated list of SEG job identifiers which consist the
69       concatenation of a UUID and a process id. The globus-fork-starter
70       program will write state changes to the SEG log using these job
71       identifiers.
72
73       For a failure, the first field of the reply is the literal 102, the
74       second field is the tag from the input, the third field is the integer
75       representation of a GRAM error code, and the fourth field is an string
76       explaining the error.
77

ENVIRONMENT

79       The following variables affect the execution of globus-fork-starter
80
81       GLOBUS_LOCATION
82           Path to the Grid Community Toolkit installation. This is used to
83           locate the globus-fork.conf configuration file.
84

FILES

86       The following files affect the execution of globus-fork-starter
87
88       /etc/globus-fork.conf
89           Path to fork SEG configuration file.
90

AUTHOR

92       Copyright © 1999-2016 University of Chicago
93
94
95
96Grid Community Toolkit 6          03/31/2018             GLOBUS-FORK-STARTE(8)
Impressum