This is a discussion on LIBPATH and cron/at within the AIX Operating System forums, part of the Unix Operating Systems category; --> Hello, On an AIX 5.3 installation, I have a LIBPATH like this in /etc/environment: LIBPATH=/usr/lib:/lib:/home/db2inst2/sqllib/lib:/home/db2inst2/sqllib/ odbc/lib However, cron/at seems ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, On an AIX 5.3 installation, I have a LIBPATH like this in /etc/environment: LIBPATH=/usr/lib:/lib:/home/db2inst2/sqllib/lib:/home/db2inst2/sqllib/ odbc/lib However, cron/at seems to strip off this environment variable before executing jobs (other stuff from /etc/environment seems to pass through to the jobs alright). Is there a way to configure cron/at to let the variable live? - Or is there another way to make aix look into additional directories for libraries? (In linux, I'd use /etc/ld.so.conf or the /etc/ld.so.conf.d directory to add library paths - does AIX have something similar?) (Of course, I could tell the users to specifically add environment- related things to their cron-jobs, but I'd rather remove unnecessary complexity.) -- Regards, Troels Arvin <troels@arvin.dk> http://troels.arvin.dk/ |
| ||||
| Troels Arvin wrote: > Hello, > > On an AIX 5.3 installation, I have a LIBPATH like this in > /etc/environment: > > LIBPATH=/usr/lib:/lib:/home/db2inst2/sqllib/lib:/home/db2inst2/sqllib/ > odbc/lib > > However, cron/at seems to strip off this environment variable before > executing jobs (other stuff from /etc/environment seems to pass through > to the jobs alright). > > Is there a way to configure cron/at to let the variable live? - Or is > there another way to make aix look into additional directories for > libraries? (In linux, I'd use /etc/ld.so.conf or the /etc/ld.so.conf.d > directory to add library paths - does AIX have something similar?) > > (Of course, I could tell the users to specifically add environment- > related things to their cron-jobs, but I'd rather remove unnecessary > complexity.) > The LIBPATH is reset on purpose is some cases, as a security measure to prevent 'trojan horse' situations. For example, see what this says about 'suid' programs: http://publib.boulder.ibm.com/infoce...etrf1/exec.htm Paul Landay |