Re: cron job problem
| From: | Jim Giner | Date: | Tue, 23 Oct 2012 22:51:01 +0000 |
| Subject: | Re: cron job problem | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-319581@lists.php.net to get a copy of this message | ||
On 10/23/2012 6:57 PM, Ashley Sheridan wrote:
On Tue, 2012-10-23 at 18:36 -0400, Jim Giner wrote:I have told them it's gotta be something on their end because I tested the script from a browser displaying what it was doing and it ran fine. Removed my debug settings and ran it from a browser and again it ran fine. Re-scheduled the cron task and it ran wrong.On 10/23/2012 6:18 PM, David OBrien wrote:Have you tried removing the job entirely from cron and re-adding it? It might be enough to kick-start the process into behaving. Yes my host asked me to do that earlier. And nope - no better.On Tue, Oct 23, 2012 at 5:31 PM, Daniel Brown <danbrown@php.net> wrote:But why now? This process has been running just fine for months.On Tue, Oct 23, 2012 at 5:34 PM, Ashley Sheridan <ash@ashleysheridan.co.uk> wrote:script runs ntp updates server time script runs again?Crontab is the daemon which runs cron jobs, and some distros have set up special files called cron.daily (or daily.cron I don't recall), cron.hourly, etc to make it easier to schedule jobs.Quick clarification and correction here:The cron *daemon* is crond, while the *script* that isbatch-processed by cron is called the crontab. When it is executed, it is referred to as a cron job.That said, Ash is right about the rest. Different OS flavors(BSD, Linux, UNIX, SunOS/Solaris, HP-UX, et cetera) often use different path and file standards. Linux, in general, uses a commandcrontabwhich opens the local user's environment-configured editor to modify the user's crontab in the spool. -- </Daniel P. Brown> Network Infrastructure Manager http://www.php.net/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php