I just removed AG 2.1.2 from my laptop, and then installed AG 2.2. I've had
two issues so far
- The GLOBUS_HOSTNAME environmental variable was still set to an
old hostname. Previously, when the venue client started up, it
would detect that GLOBUS_HOSTNAME wasn't set to a hostname that
was valid for one of the interfaces and bring up a dialoge box
to properly set it. Now, though, various bits and pieces just
try to talk to a hostname that doesn't map to any of the local
interfaces, and isn't even up.
- Even though the shortcut in the start menu specifies
--personalNode, I had to start up agservicemanager and
agnodeservice manually before I could do anything.
Are either of these known issues at all, or should I bugzilla them?
--
Frank Sweetser fs at wpi.edu
WPI Network Engineer
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
