I've got a question about the following cronjob.
#At 3:01 our time, run backups
1 0 * * * /usr/local/bin/php /www/r/rester/htdocs/auto_backup/back_em_up.php
/www/r/rester/htdocs/auto_backup/cron.log 21
#At 3:02 clean up sessions folder
2 0 * * * (find /www/r/rester/htdocs/sessions/ -name 'sess_*'
[snip]
I've got a question about the following cronjob.
#At 3:01 our time, run backups
1 0 * * * /usr/local/bin/php
/www/r/rester/htdocs/auto_backup/back_em_up.php
/www/r/rester/htdocs/auto_backup/cron.log 21
#At 3:02 clean up sessions folder
2 0 * * * (find /www/r/rester/htdocs/sessions/
Jay Blanchard wrote:
[snip]
I've got a question about the following cronjob.
#At 3:01 our time, run backups
1 0 * * * /usr/local/bin/php
/www/r/rester/htdocs/auto_backup/back_em_up.php
/www/r/rester/htdocs/auto_backup/cron.log 21
#At 3:02 clean up sessions folder
2 0 * * * (find
Al wrote:
I've got a question about the following cronjob.
#At 3:01 our time, run backups
1 0 * * * /usr/local/bin/php
/www/r/rester/htdocs/auto_backup/back_em_up.php
/www/r/rester/htdocs/auto_backup/cron.log 21
#At 3:02 clean up sessions folder
2 0 * * * (find /www/r/rester/htdocs/sessions/
#this is only for testing a new cronjob, every minute
* * * * * /usr/local/bin/php
/www/r/rester/htdocs/phpList_cronjob/process_cronjob.php
/www/r/rester/htdocs/phpList_cronjob/cron.log 21
The new one doesn't seem to want to run until after 3:01 or 3:02.
Shouldn't the
sever just run it
Erwin Kerk wrote:
Al wrote:
I've got a question about the following cronjob.
#At 3:01 our time, run backups
1 0 * * * /usr/local/bin/php
/www/r/rester/htdocs/auto_backup/back_em_up.php
/www/r/rester/htdocs/auto_backup/cron.log 21
#At 3:02 clean up sessions folder
2 0 * * * (find
On Mon, 2005-01-17 at 09:01, Erwin Kerk wrote:
Al wrote:
I've got a question about the following cronjob.
#At 3:01 our time, run backups
1 0 * * * /usr/local/bin/php
/www/r/rester/htdocs/auto_backup/back_em_up.php
/www/r/rester/htdocs/auto_backup/cron.log 21
#At 3:02 clean up
Erwin Kerk wrote:
The CRON daemon only refreshes it's job list after a job in the
current list is completed. Therefore, the CRON daemon won't notice the
every-minute job until 3.01 pm.
I'm not sure I understand what you're saying above. Can you provide a pointer
to
documentation about this?
On Monday 17 January 2005 23:19, Al wrote:
Erwin Kerk wrote:
Al wrote:
The CRON daemon only refreshes it's job list after a job in the current
list is completed. Therefore, the CRON daemon won't notice the
every-minute job until 3.01 pm.
Not sure if I've misunderstood what Al is saying
Michael Sims wrote:
Erwin Kerk wrote:
The CRON daemon only refreshes it's job list after a job in the
current list is completed. Therefore, the CRON daemon won't notice the
every-minute job until 3.01 pm.
I'm not sure I understand what you're saying above. Can you provide a pointer
to
Jochem Maas wrote:
Michael Sims wrote:
Additionally, cron checks each minute to see if its spool
directory's modtime (or the modtime on /etc/crontab) has changed,
and if it has, cron will then examine the modtime on all crontabs
and reload those which have changed. Thus cron need not be
Michael Sims wrote:
Erwin Kerk wrote:
The CRON daemon only refreshes it's job list after a job in the
current list is completed. Therefore, the CRON daemon won't notice the
every-minute job until 3.01 pm.
I'm not sure I understand what you're saying above. Can you provide a pointer
to
Michael Sims wrote:
Jochem Maas wrote:
Michael Sims wrote:
Additionally, cron checks each minute to see if its spool
directory's modtime (or the modtime on /etc/crontab) has changed,
and if it has, cron will then examine the modtime on all crontabs
and reload those which have changed. Thus
13 matches
Mail list logo
