1GLOBUS-PERSONAL-GA(1)    Grid Community Toolkit Manual   GLOBUS-PERSONAL-GA(1)
2
3
4

NAME

6       globus-personal-gatekeeper - Manage a user's personal gatekeeper daemon
7

SYNOPSIS

9       globus-personal-gatekeeper [-help ] [-usage ] [-version ] [-versions ]
10       [-list ] [-directory CONTACT]
11

DESCRIPTION

13       The globus-personal-gatekeeper command is a utility which manages a
14       gatekeeper and job manager service for a single user. Depending on the
15       command-line arguments it will operate in one of several modes. In the
16       first set of arguments indicated in the synopsis, the program provides
17       information about the globus-personal-gatekeeper command or about
18       instances of the globus-personal-gatekeeper that are running currently.
19       The second set of arguments indicated in the synopsis provide control
20       over starting a new globus-personal-gatekeeper instance. The final set
21       of arguments provide control for terminating one or more
22       globus-personal-gatekeeper instances.
23
24       The -start mode will create a new subdirectory of $HOME/.globus and
25       write the configuration files needed to start a and write the
26       configuration files needed to start a globus-gatekeeper daemon which
27       will invoke the globus-job-manager service when new authenticated
28       connections are made to its service port. The
29       globus-personal-gatekeeper then exits, printing the contact string for
30       the new gatekeeper prefixed by GRAM contact: to standard output. In
31       addition to the arguments described above, any arguments described in
32       globus-job-manager(8) can be appended to the command-line and will be
33       added to the job manager configuration for the service started by the
34       globus-gatekeeper.
35
36       The new globus-gatekeeper will continue to run in the background until
37       killed by invoking globus-personal-gatekeeper with the -kill or
38       -killall argument. When killed, it will kill the globus-gatekeeper and
39       globus-job-manager processes, remove state files and configuration
40       data, and then exit. Jobs which are running when the personal
41       gatekeeper is killed will continue to run, but their job directory will
42       be destroyed so they may fail in the LRM.
43
44       The full set of command-line options to globus-personal-gatekeeper
45       consists of:
46
47       -help, -usage
48           Print command-line option summary and exit
49
50       -version
51           Print software version
52
53       -versions
54           Print software version including DiRT information
55
56       -list
57           Print a list of all currently running personal gatekeepers. These
58           entries will be printed one per line.
59
60       -directory CONTACT
61           Print the configuration directory for the personal gatekeeper with
62           the contact string CONTACT.
63
64       -debug
65           Print additional debugging information when starting a personal
66           gatekeeper. This option is ignored in other modes.
67
68       -start
69           Start a new personal gatekeeper process.
70
71       -jmtype LRM
72           Use LRM as the local resource manager interface. If not provided
73           when starting a personal gatekeeper, the job manager will use the
74           default fork LRM.
75
76       -auditdir AUDIT_DIRECTORY
77           Write audit report files to AUDIT_DIRECTORY. If not provided, the
78           job manager will not write any audit files.
79
80       -port PORT
81           Listen for gatekeeper TCP/IP connections on the port PORT. If not
82           provided, the gatekeeper will let the operating system choose.
83
84       -log[=DIRECTORY]
85           Write job manager log files to DIRECTORY. If DIRECTORY is omitted,
86           the default of $HOME will be used. If this option is not present,
87           the job manager will not write any log files. will be used. If this
88           option is not present, the job manager will not write any log
89           files.
90
91       -seg
92           Try to use the SEG mechanism to receive job state change
93           information, instead of polling for these. These require either the
94           system administrator or the user to run an instance of the
95           globus-job-manager-event-generator program for the LRM specified by
96           the -jmtype option.
97
98       -acctfile ACCOUNTING_FILE
99           Write gatekeeper accounting entries to ACCOUNTING_FILE. If not
100           provided, no accounting records are written.
101

EXAMPLES

103       This example shows the output when starting a new personal gatekeeper
104       which will schedule jobs via the lsf LRM, with debugging enabled.
105
106           % globus-personal-gatekeeper -start -jmtype lsf
107
108           verifying setup...
109           done.
110           GRAM contact: personal-grid.example.org:57846:/DC=org/DC=example/CN=Joe User
111
112       This example shows the output when listing the current active personal
113       gatekeepers.
114
115           %  globus-personal-gatekeeper -list
116           personal-grid.example.org:57846:/DC=org/DC=example/CN=Joe User
117
118       This example shows the output when querying the configuration directory
119       for the above personal gatekeeper. gatekeepers.
120
121           %  globus-personal-gatekeeper -directory "personal-grid.example.org:57846:/DC=org/DC=example/CN=Joe User"
122           /home/juser/.globus/.personal-gatekeeper.personal-grid.example.org.1337
123
124           %  globus-personal-gatekeeper -kill "personal-grid.example.org:57846:/DC=org/DC=example/CN=Joe User"
125           killing gatekeeper: "personal-grid.example.org:57846:/DC=org/DC=example/CN=Joe User"
126

SEE ALSO

128       globusrun(1), globus-job-manager(8), globus-gatekeeper(8)
129

AUTHOR

131       Copyright © 1999-2016 University of Chicago
132
133
134
135Grid Community Toolkit 6          03/31/2018             GLOBUS-PERSONAL-GA(1)