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);
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|