davidg, but ownership should
be transferred to a `grid admin' account that is also part of the
ices group. This account is prevents to Globus install base and
information services from being tampered with. This new account should
under no circumstance be used to run the Gatekeeper!
The microgrid consists of: bilbo (GIIS), bombur, triplex, triomf
(currently not active).
The following patches were applied to the Globus 1.1.3 system:
globus-gass-cache by hand for each architecture.
A faulty configure.in `forgets' this cache management tool.
You can build by hand using the Makefiles from the
DevelopersTutorial.etc/grid-security.conf file contains a typo. Modify the
line GSI_CA_EMAIL_ADDR by including the forgotten CA_.globusrun.c
suggested on the discuss mailing list (subject: Re:
Problem with globus-job-clean).
On some hosts a simple perl-based daemon (in.gsd) will answer quesries
about the current load and utilisation of the system. It will also
report on the status of a potential Gatekeeper. The daemon listens on
port 52493. A graphical user interface (gsm-0.1) will visualise the
results. The daemon is liable to denial-of-service attacks (it
can be killed remotely), but is otherwise secure: it cannot be lured
into doing any more than printing the system load. It is not part of
the Globus toolkit and used for monitoring the microgrid testbed only.