In message <f99bc0a7-33d3-4501-a8b4-17ed5764e...@pharmacy.arizona.edu>, Bruce J ohnson writes: >This is functioning, since no errors came up.
If "env -i /path/to/shell/script" works from the command-line, then /path/to/shell/script will work from cron. >One quick perl-related question, though what environment do perl modules import >ed via use module; commands have? I would think it was the environment of >the >importing program. Correct, though as you learned back in October when trying to configure your environment for Apache and modperl, you must take care to set the environment before the module is imported. >One of the use statements has an exported function that checks something in th >e database, and there is a db connection made if the function is called. The e >rror line number doesnt make sense, since the error refers to the line making >my db connection in the main script, and doesnt correspond to an existing line > in the perl module, but Ive run into oddball misdirections in perl error stat >ements in the past. A short reproducable example with SCOTT's demo schema would help me understand what you mean. John groenv...@acm.org
