globus-personal-gatekeeper(1)

1GLOBUS-PERSONAL-GA(1)           GRAM5 Commands           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
12       globus-personal-gatekeeper [-debug] {-start} [-jmtype LRM]
13                                  [-auditdir AUDIT_DIRECTORY] [-port PORT]
14                                  [-log [=DIRECTORY]] [-seg]
15                                  [-acctfile ACCOUNTING_FILE]
16
17       globus-personal-gatekeeper [-killall] [-kill]
18

DESCRIPTION

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

EXAMPLES

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

NAME

SYNOPSIS

DESCRIPTION

EXAMPLES

SEE ALSO