Linux 5.1.5.14-client

2003-02-19 Thread Tom Tann{s 
Hello *SM'ers!

Is there a problem/bug in the libPiSNAP.so and/or libPiIMG.so?

We don't use the default installation-path, but DSM_DIR, DSMI_DIR etc are
set to the right paths.

dsmc generated these entries in dsmerror.log:

02/19/2003 20:18:45 dlopen() of /local/tsm/bin/plugins/libPiSNAP.so failed.
02/19/2003 20:18:45 libApiDS.so: cannot open shared object file: No such file or 
directory.
02/19/2003 20:18:45 dlopen() of /local/tsm/bin/plugins/libPiIMG.so failed.
02/19/2003 20:18:45 libApiDS.so: cannot open shared object file: No such file or 
directory.


DSM_DIR=/local/tsm/bin
DSMI_DIR=/local/tsm/api/bin


tarcil.uio.no# ls -al $DSMI_DIR/libApiDS.so
-r-xr-xr-x1 root root  1884550 Feb 18 16:05 /local/tsm/api/bin/libApiDS.so
tarcil.uio.no#


The default installation creates a symlink,
/usr/lib/libApiDS.so - /opt/tivoli/tsm/client/api/bin/libApiDS.so

After creating a

/usr/lib/libApiDS.so - /local/tsm/api/bin/libApiDS.so, things seem to
work fine.

But the DSMI_DIR should make this unneccesary, shouldn't it?

So..
Has anyone else come across this? Have I missed something basically here?

Any suggestions, comments, etc on this would be appreciated.

Tom.

Re: Linux 5.1.5.14-client

2003-02-19 Thread Dan Foster 
Hot Diggety! Tom Tann{s was rumored to have written:
 Hello *SM'ers!

 Is there a problem/bug in the libPiSNAP.so and/or libPiIMG.so?

 We don't use the default installation-path, but DSM_DIR, DSMI_DIR etc are
 set to the right paths.

 dsmc generated these entries in dsmerror.log:
 
 02/19/2003 20:18:45 dlopen() of /local/tsm/bin/plugins/libPiSNAP.so failed.
 02/19/2003 20:18:45 libApiDS.so: cannot open shared object file: No such file or 
directory.

You have two options:

1. set up symlinks to /usr/lib then do 'ldconfig'

or...

2. add /local/tsm/bin/plugins to /etc/ld.so.conf then do 'ldconfig'

-Dan