Aaron Taylor wrote:
-bash-3.00$ ldd amcheck <--As user amanda
<snip>
libgcc_s.so.1 => (file not found)
libgcc_s.so.1 => (file not found)
libgcc_s.so.1 => (file not found)
<snip>
bash-3.00# ldd amcheck <--As user root
<snip>
libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
<snip>
Also, as before, the PATH and LD_LIBRARY_PATH variables are identical
for the two sessions.
I appreciate the suggestion though. I hadn't checked that yet.
Some random tips and checks:
Is there a space character after the variable? Like in:
$ LD_LIBRARY_PATH="/usr/lib:/usr/local/lib "; export LD_LIBRARY_PATH
$ echo "x${LD_LIBRARY_PATH}x"
x/usr/lib:/usr/local/lib x
You did "export" the variable for user amanda, did you?
Try the "ldd -s amcheck" to find out where it tries to find the module.
What is the difference when running as root vs. amanda?
Is it compiled as a 64-bit application?
Use the command "crle" and "crle -64" to find out the difference.
Is there a libgcc_s.so.1 accessible as amanda in the 64-bit environment?
Use "crle -u -l /usr/local/lib" to update the default search path,
instead of using LD_LIBRARY_PATH.
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|