Here is a piece of code for you:
#!/usr/bin/perl -w
use strict;
my $mode=shift @ARGV;
my $logfile=sprintf("/tmp/%s-env.txt",$mode);
open FOUT,"> $logfile" or die "$logfile: $!";
foreach my $key ( sort keys %ENV){
printf FOUT "%s = \"%s\"\n",$key,$ENV{$key};
}
close FOUT;
system(sprintf "umask >> %s",$logfile);
system(sprintf "id >> %s",$logfile);
system(sprintf "pwd >> %s",$logfile);
exit(0);
Don't forget to
$ chmod 755 /path/to/my/script/above.pl so it can run. First run it as a "batch" job
$ echo "/path/to/my/script/above.pl ascron" | at now
which will be the same environment as a cronjob would be.
Then run it from the command line:
$ /path/to/my/script/above.pl ascmdlin
then check the differences:
diff /tmp/ascron-env.txt /tmp/ascmdlin-env.txt
and that should help you rule some stuff out.
Typically the difference between command line and cron has to do with permissions or environment being different. It ain't rocket science.
Peter L. Berghold -- Unix Professional
Peter -at- Berghold -dot- Net; AOL IM redcowdawg Yahoo IM: blue_cowdawg
-
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.