1GLOBUS-SCHEDULER-E(8)    Grid Community Toolkit Manual   GLOBUS-SCHEDULER-E(8)
2
3
4

NAME

6       globus-scheduler-event-generator - Process job state change events
7

SYNOPSIS

9       globus-scheduler-event-generator -h
10
11       globus-scheduler-event-generator -s LRM_NAME [OPTIONS]
12

DESCRIPTION

14       The globus-scheduler-event-generator (SEG) is a program which uses
15       local resource manager-specific monitoring modules to generate job
16       state change events. At the SEG level, the state change events
17       correspond to changes in any jobs which are managed by the scheduler,
18       even if they do not correspond to jobs initiated by the GRAM5 Service.
19       These state change events are propagated to the Job State Monitor.
20
21       Depending on scheduler-specific requirements, the SEG may need to run
22       with privileges to enable it to obtain scheduler event notifications.
23       As such, one SEG runs per scheduler resource. For example, on a host
24       which provides access to both PBS and fork jobs, two SEGs, running at
25       (potentially) different privilege levels will be running.
26
27       When executed, the SEG is able to start issuing events from some time
28       in the past. The SEG will, in general, not require any persistent state
29       between invocations. One SEG instance exists for any particular
30       scheduled resource instance (one for all homogeneous PBS queues, one
31       for all fork jobs, etc).
32
33       The SEG is implemented in an executable called the
34       globus-scheduler-event-generator, located in the Grid Community
35       Toolkit’s sbin directory.
36
37       When begun, it loads the LRM-specific module based on the LRM_NAME
38       parameter, and then defers to it for most functionality. When it
39       detects an error writing to stdout or reading stdin, it terminates. The
40       LRM-specific code uses the SEG API to emit events to the GRAM5 service.
41

OPTIONS

43       -h
44           Display a help message and exit.
45
46       -s LRM_NAME
47           Load the LRM-specific module for LRM_NAME. This is translated to
48           loading the dynamic library libglobus_seg_’LRM_NAME'.
49
50       -t TIMESTAMP
51           Process events starting at TIMESTAMP. This is the only way to get
52           the globus-scheduler-event-generator to process events that occur
53           before the process begins. If not specified, it will generate
54           events from the current timestamp only.
55
56       -d DIRECTORY
57           Write job state change events to files in DIRECTORY, named by the
58           day that the event occurred (DIRECTORY/YYYYMMDD); if not specified,
59           the events will be written to standard output.
60
61       -b
62           Run in the background. This only works if the -d option above is
63           used.
64
65       -p PIDFILE
66           Write the process id of the globus-scheduler-event-generator to
67           PIDFILE.
68

AUTHOR

70       Copyright (c) 1999-2014 University of Chicago
71
72
73
74Grid Community Toolkit 6          03/31/2018             GLOBUS-SCHEDULER-E(8)
Impressum