cron doesn't give control back to the script after the wget.
What do you mean by that? Cron isn't somekind of god that
picks apart a program and deals with each piece of code
individually. All that cron does is look at its watch,
say "it's 10 minutes past 4!", fork, set (e)uid and pipe-open
/root/crons/downloadsyncs.pl. Cron doesn't care
what kind of external programs the script calls, and it
certainly won't call those programs on the scripts behalf.
What you should be aware of when calling programs from cron
(any program, not just Perl programs), is that you
will have a limited environment. There's no user calling the
program, and there's no login-shell involved either. There
won't be many environment variables, PATH will likely be
different than running something from the command-line, and
so will your current working directory.
Abigail
-
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.
|