The common way to do this is "source $GLOBUS_LOCATION/etc/globus-user-
env.sh". It sets up the appropriate library variable for whatever
system you're on.
Charles
On Jul 17, 2008, at 10:25 AM, Martin Feller wrote:
Hi,
Did you install from a binary installer?
If so, you'll have to add $GLOBUS_LOCATION/lib to the environment
variable LD_LIBRARY_PATH before starting the container.
Example for bash:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$GLOBUS_LOCATION/lib
To make this permanent you can set the LD_LIBRARY_PATH in your shell
init file (e.g. .bashrc).
Martin
Carlos wrote:
Hi:
I've just installed the Globus 4.0.7 full version to execute my
grid applications. But when I start the globus container I get the
following message again and again each ten seconds. In this sense,
my applications get errors that (I think) are related to this
error. What's wrong? I tried other versions and it did not happen.
17-jul-2008 16:48:48
org.globus.exec.monitoring.SchedulerEventGenerator run
GRAVE: SEG Terminated with /usr/local/globus-4.0.7/libexec/globus-
scheduler-event-generator: error while loading shared libraries:
libglobus_scheduler_event_generator_gcc32.so.0: cannot open shared
object file: No such file or directory
Thanks in advance
Carlos
_________________________________________________________________
Sigue en directo todas las competiciones deportivas en MSN Deportes
http://deportes.es.msn.com/
