Hi, John. Typically, instead of setting this variable globally, you would set it in a script before it calls dsmc, that way the variable's only set until the script ends. Only if you're running this as a dedicated service user, or only if it doesn't break anything, would I recommend setting the variable in the user's .kshrc, .bashrc, .bash_profile, .profile, or whatever.
On 10/4/2012 11:39 AM, Underdown,John William wrote:
Hi All, i'm having a problem with setting LD_LIBRARY_PATH variable on a Linux box for backing up VM's see below. any guidance on this would be most appreciated. Thanks. Problem Details . Product or Service: Tivoli Storage Manager Client Linux 6.3.L Component ID: 5698ISMCL . Operating System: Linux . Problem title ans8810E setting LD_LIBRARY_PATH . Problem description on RHEL 5.x i would set the LD_LIBRARY_PATH globally in the login profile. on RHEL 6.x when i do that, it breaks many of the RHEL commands., see below. what is the best way to set the LD_LIBRARY_PATH variable? # yum update Fatal Python error: pycurl: libcurl link-time version is older than compile-time version Aborted (core dumped) Red Hat Enterprise Linux Server release 6.3 (Santiago) 2.6.32-279.9.1.el6.x86_64 TSM Client Version 6, Release 3, Level 0.15 ----------------------------------------- NOTICE: This communication is intended only for the person or entity to whom it is addressed and may contain confidential, proprietary, and/or privileged material. Unless you are the intended addressee, any review, reliance, dissemination, distribution, copying or use whatsoever of this communication is strictly prohibited. If you received this in error, please reply immediately and delete the material from all computers. Email sent through the Internet is not secure. Do not use email to send us confidential information such as credit card numbers, PIN numbers, passwords, Social Security Numbers, Account numbers, or other important and confidential information.
