On Feb 6, 2008, at 11:09 AM, Giuseppe Fiameni wrote:
Dear Charles
I believe that should be pointing the path to the LoadLeveler log
file. Only globus-fork writes out a logfile of events. All the
other schedulers rely on libexec/globus-scheduler-event-generator
to output events at runtime.
I am not quite sure because this would mean that the LoadLeveler
log file should be writable by any user that can submit job on my
machine :(
No. As I explained, nobody writes to that file. The SEG needs to
know where to read from.
To simulate what the container will see, run:
libexec/globus-scheduler-event-generator -s <scheduler_type> -t 1
The scheduler_type should match the spelling/capitalization in etc/
gram-service-<scheduler_type>
I think that scheduler_type should match with seg libraries
convention because when the globus-scheduler-event-generator
starts it tries to load /
libglobus_seg_<scheduler_type>_<compiler><flavor>.la/ library.
Anyway, when I run that command I do not see anything :(
Are you pointing to the Loadleveler log with the log_path?
Charles
