Hi all,

I'm not using a config file into /etc/ld.so.conf.d directory since I've 
experienced some conflicts with Debian 6 (libcrypto.so.0.9.8).

I'm now using symlinks only, as the RPM package does :


root@ubuntu:/opt/tivoli/tsm/client/ba/bin# ldd dsmc
        linux-vdso.so.1 =>  (0x00007ffff71fe000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 
(0x00007fc8724c6000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x00007fc8722a9000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc8720a4000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x00007fc871da0000)
        libgpfs.so => /usr/lib/libgpfs.so (0x00007fc871c96000)
        libdmapi.so => /usr/lib/libdmapi.so (0x00007fc871b8e000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fc871986000)
        libgsk8ssl_64.so => /usr/lib/libgsk8ssl_64.so (0x00007fc871732000)
        libgsk8iccs_64.so => /usr/lib/libgsk8iccs_64.so (0x00007fc8715d0000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc8712cc000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x00007fc8710b6000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc870ced000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fc872706000)
        libgsk8cms_64.so => /usr/lib/libgsk8cms_64.so (0x00007fc8708d1000)
        libgsk8sys_64.so => /usr/lib/libgsk8sys_64.so (0x00007fc8707ce000)

root@ubuntu:/opt/tivoli/tsm/client/ba/bin# ls -l /usr/lib/ | egrep -i 'tsm|ibm'
lrwxrwxrwx  1 root root      52 Sep  4 22:32 libApiTSM64.so -> 
../../opt/tivoli/tsm/client/api/bin64/libApiTSM64.so
lrwxrwxrwx  1 root root      44 Nov  6 01:51 libdmapi.so -> 
/opt/tivoli/tsm/client/api/bin64/libdmapi.so
lrwxrwxrwx  1 root root      43 Nov  6 01:51 libgpfs.so -> 
/opt/tivoli/tsm/client/api/bin64/libgpfs.so
lrwxrwxrwx  1 root root      50 Nov  6 01:51 libgsk8acmeidup_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8acmeidup_64.so
lrwxrwxrwx  1 root root      45 Nov  6 01:51 libgsk8cms_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8cms_64.so
lrwxrwxrwx  1 root root      46 Nov  6 01:51 libgsk8dbfl_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8dbfl_64.so
lrwxrwxrwx  1 root root      46 Nov  6 01:51 libgsk8drld_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8drld_64.so
lrwxrwxrwx  1 root root      46 Nov  6 01:51 libgsk8iccs_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8iccs_64.so
lrwxrwxrwx  1 root root      46 Nov  6 01:51 libgsk8kicc_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8kicc_64.so
lrwxrwxrwx  1 root root      44 Nov  6 01:51 libgsk8km_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8km_64.so
lrwxrwxrwx  1 root root      46 Nov  6 01:51 libgsk8ldap_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8ldap_64.so
lrwxrwxrwx  1 root root      45 Nov  6 01:51 libgsk8p11_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8p11_64.so
lrwxrwxrwx  1 root root      45 Nov  6 01:51 libgsk8ssl_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8ssl_64.so
lrwxrwxrwx  1 root root      45 Nov  6 01:51 libgsk8sys_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8sys_64.so
lrwxrwxrwx  1 root root      46 Nov  6 01:51 libgsk8valn_64.so -> 
/usr/local/ibm/gsk8_64/lib64/libgsk8valn_64.so
lrwxrwxrwx  1 root root      57 Sep  4 22:32 libtsm641xerces-c1_6_0.so -> 
../../opt/tivoli/tsm/client/api/bin64/libxerces-c1_6_0.so
lrwxrwxrwx  1 root root      59 Sep  4 22:32 libxmlutil-6.4.1.0.so -> 
../../opt/tivoli/tsm/client/api/bin64/libxmlutil-6.4.1.0.so

-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

----- Mail original -----
De: "Christian Schmidt" <Christian.Schmidt AT CHEMIE.UNI-HAMBURG DOT DE>
À: ADSM-L AT VM.MARIST DOT EDU
Envoyé: Mercredi 6 Novembre 2013 09:30:38
Objet: Re: [ADSM-L] dsmc dumps core on Ubuntu 13.10 amd64

Hi all,

05.11.2013 21:19, Stephan Rumpfhuber:
> I have exactly the same problem. I have several systems running ubuntu
> 13.10 but not all were affected. It seems to be that this have something
> todo with the password file and the client crashes when it tries to read
> or write the file (this just a guess) . By changing the passwordaccess
> option to “prompt” instead of “generate” the problem doesn't occur anymore.

I gave this a try. In addition, I added /usr/local/ibm/gsk8_64/lib64 to
my /etc/ld.so.conf.d/adsm.conf. Now dsmc launches without problems.

It's running in a screen session now. We'll see what happens when the
schedule is due.

Thank you (all!) very much!

Regards,
Christian

-- 
No signature available.