Comments on: Prevent scripts from being killed

By: Juozas

Juozas — Fri, 27 Mar 2009 17:29:00 +0000

Because of hosting provider I use – I have no access to shell; CRON jobs are ran with wget, not cli.

By: Adam L

Adam L — Fri, 27 Mar 2009 17:26:44 +0000

I don’t understand why you just don’t run the command from the Command Line?

By: Juozas Kaziukenas’ Blog: Prevent scripts from being killed : Dragonfly Networks

Fri, 27 Mar 2009 04:51:41 +0000

[...] Kaziukenas has a helpful tip you can use on those long-running scripts to keep going – the set_time_limit [...]

By: Juozas Kaziukenas’ Blog: Prevent scripts from being killed : WebNetiques, LLC : Website Developers in Minneapolis, MN

Fri, 27 Mar 2009 04:49:07 +0000

[...] Kaziukenas has a helpful tip you can use on those long-running scripts to keep going – the set_time_limit [...]

By: Juozas Kaziukenas’ Blog: Prevent scripts from being killed | Development Blog With Code Updates : Developercast.com

Thu, 26 Mar 2009 19:20:17 +0000

[...] Kaziukenas has a helpful tip you can use on those long-running scripts to keep going – the set_time_limit function. I have [...]

By: Wesley

Wesley — Thu, 26 Mar 2009 07:16:36 +0000

I do the same, except disable output compression. Smart, I will add (remove) that from my scripts as well. (Though they typically don’t output anything)

I do think that the apache_setenv line could be removed, since you typically execute these php cron jobs via the CLI (command line interface) and not via wget http://url/script.php

By: Giorgio Sironi

Giorgio Sironi — Wed, 25 Mar 2009 22:06:16 +0000

Nice, while I never understand why php permits to set memory limit in the script itself while a 1kb file cannot be written (without using chmod before)…