Tom Allison wrote: > Wiggins d'Anconia wrote: > >> Normally you add to the @INC using the PERL5LIB environment variable. If >> "oracle>" represents a normal bash shell, then, >> >> export PERL5LIB="/path/to/lib/dir" >> >> Should do the trick. If it is actually the Oracle client then you might >> try the same because *theoretically* the subprocess should inherit and >> respect the same environment. >> > > I'm trying to do the same under a Solaris install at work and for some > reason that I can't find ( insufficient man pages on box ), I can't get > my Environment of ~/.profile to be recognized from crontab entries. > > Any other options under Solaris that I should try? > > I know, I'm on the OT fringe here, maybe someone can give me an answer > using perl -i ?? :) >
I ran into the same problem. In general to my knowledge cron for security reasons uses what is essentially an empty environment subshell, and won't source any profiles. I know we accomplished the same task, but don't have specifics. Try adding an export of the environment to the beginning of your crontab command line, and separate it with semi-colons as if you were issuing a single command, similar to, * * * * * export PERL5LIB=/path/to/dir; /run/your/command See if that works. I know it is possible with Solaris' cron but I know we had to mess with it for a while. If you have compiled modules with a C component you may also have to mess with the LD_* environment variables, we had to. HTH, http://danconia.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
