On 6/2/05, fire-eyes <[EMAIL PROTECTED]> wrote: > On Thu, 2005-06-02 at 14:54 -0400, Dave Nebinger wrote: > > Sometimes there are environmental differences that are not immediately > > obvious between executing a command at the shell vs. within a cron task. > > > > A great hint I saw was to use the 'sys-process/at' package's command to > > schedule the script to run some time in the future. Then go to the > > /var/spool/at/atjobs folder to find a new script that has the environment > > configured correctly from the environment used to schedule the job. > > > > Use that script in your cron task to have a correct environment for the cron > > task. > > > > Dave > > Guess I'll give that a shot at some point. Might sourcing /etc/profile > help?
invoking a login shell will cause loading all your environmental variables correctly. so, instead of invoking /path/to/shell.sh use sh -l /path/to/shell.sh -- gentoo-user@gentoo.org mailing list
