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.
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>
Charles
On Feb 6, 2008, at 10:54 AM, Giuseppe Fiameni wrote:
Dear all,
I would like also to ask you a brief clarification. Which file has
to be specified with log_path attribute into globus-
loadleveler.conf file ?
Am I requested to put there the path of LoadLeveler log file (say /
var/loadl/log/SchedLog)
or I can indicate the path of a new file ? Must this file be
writable by both Globus container and LoadLeveler ?
I resolved my doubt and right now I knowledge that the log file
that has to be indicated
into /globus-loadleveler.conf/ could be an arbitrary one.
But, who is that file expected to be written by ?
I noticed that when I submit jobs no entries like
01;1149181338;node01.test.com.44.0;2;0
appear in that file.
I have to modify Load Leveler configuration in order
to report job status there ?
Any help is really appreciate.
Many thanks.
Giuseppe
