The past week was a frustrating one for me. Cronless was bounced around inside my ISP to a new VPS server. The end result is all good now, but there was some time where emails were NOT going out notifying you about your jobs because of configuration changes. The jobs ran, but no notices appeared. My apologies to everyone for that. The problem has been fixed and we’re moving forward again.
Development Blog for Cronless.com
Archive for October, 2009
Cronless moved to a new VPS
Saturday, October 31st, 2009Tips Creating Your Jobs
Thursday, October 15th, 2009It’s quite possible that you may get timeouts when your PHP cron job runs. If that happens, place this at the top of your script
<?php
set_time_limit(0); //0 = run forever
?>
This will allow your script to run to completion, ignoring timeouts. Jobs executed here at Cronless are run under this directive, but your own web server may timeout if you fail to put that in as well!
If you find that this isn’t enough and you still get timeouts (some hosts are disabling this PHP function), you can help by limiting your script output as much as possible. (less than 4kb is ideal)
Survey Says: Better Notifications
Saturday, October 10th, 2009Our recent survey has come back with some great feedback, including:
- More options for notifications (GTalk, AIM, Yahoo)
- Send emails with clear SUCCESS/FAILURE in title (for mobile users)
- Update job setup to use a calendar widget instead of UNIX timestamp entry
Well, you spoke and we’re listening. These features are being implemented in the coming weeks. Keep your eye out for changes!