Closed marcmengel closed 1 year ago
So it turns out just clearing LD_LIBRARY_PATH before calling condor executables isn't sufficient, because we
import htcondor
and that will give an error like this if the LD_LIBRARY_PATH has a libuuid in it
We could clear LD_LIBRARY_PATH and re-exec python if it is set before doing any actual work...
This also would break if someone was doing -e LD_LIBRARY_PATH
to pass the current LD_LIBRARY_PATH to their jobs, as it would then show up blank, although we could special-case it, and rename LD_LIBRARY_PATH in the environment...
In any case this is uglier than I first thought. Sigh.
Okay, so I found a way to test this:
mkdir /tmp/biteme
dd if=/usr/lib64/libuuid.so.1 of=/tmp/biteme/libuuid.so.1 count=1
export LD_LIBRARY_PATH=/tmp/biteme:$LD_LIBRARY_PATH
Clear LD_LIBRARY_PATH before calling condor exectuables.