Are you not able to see the output of the cron job? The output should be logged somewhere or sent in an email - that depends on your hosting environment.
If you can't find that, you could move your command to a shell script that is referenced by the crontab. You can add code in that script to inspect the environment and/or capture the output of your rake command in your own log file. But you could use a little more information to help track down the problem. On Aug 31, 6:13 am, bingo bob <[email protected]> wrote: > Maybe, just unsure what. Annoying as it's stopping me doing lots of rake > stuff on a schedule. > > I mean I know there are solutions to run background tasks in the app but > I didn't really want the memory overhead for now and this seems like a > quick win. If "only" I could get it working! > > Any ideas what else I could try anyone? > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
