Unix crons often run into problems with an incorrectly set environment that causes the same script which works fine for you to break when used in the cron.

Under the assumption that you don't have a bizarre default login environment (eg = in the variable names or returns in the values) and your standard shell is bash, the following snippet demonstrates how you could load the default values from your login environment into your current, without losing other values that might have been passed in your cron.

use strict;
sub get_bash_login_env {
  local %ENV;
  my $env = `echo env | bash --login`;
  if (wantarray) {
    $env =~ s/\\(.)/$1/gs;
    return map {split /=/, $_, 2} map {split /\n/, $_} $env;
  }
  else {
    return $env;
  }
}

# And a demo of how to use it

use Data::Dumper;
%ENV = (%ENV, get_bash_login_env());
print Dumper(\%ENV);
[download]