[no subject]

First thing to check is env.  The cron env is limited, thus it might be 
failing because of path issues.  Do you get any email regarding the job? 
  Redirect some info to stderr and stdout.  You should receive email 
with this info.

Also, take the same approach with a very simple script to see if maybe 
there's something wrong with the webmin scheduling.  Something like:

date > /tmp/crontest

-- 
Until later, Geoffrey


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00605" href="msg00605.html">[ale] Cron Job that will not run</a></strong>
<ul><li><em>From:</em> jeb at rev-x.com (Jeb Barger)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00606.html">[ale] WiFi PC Card Market</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00608.html">[ale] OT but funny</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00605.html">[ale] Cron Job that will not run</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00612.html">[ale] Cron Job that will not run</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00607"><strong>Date</strong></a></li>
<li><a href="threads.html#00607"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>