On Nov 19, 3:46 pm, "Ivor Paul" <[EMAIL PROTECTED]> wrote:
> Cool, thanks
>
> I compared my email to the other emails that came after mine and just
> wondered what the difference was. I do realize that this isn't a very
> general problem. Im sitting at GMT +2 so didn't realise how early it
> was in im guessing the east coast of the usa.
>
The other thing is how many people are using bj ( I for example have
never used it). You may find that there are more people using it on
ruby-talk
>
> However, the jobs are never executed. It feels like what ever couping
> there was with Bj and the script/server is missing.
>
> Bj.runner.ping
> => nil
>
> Bj.runner.tickle
> => {"pid"=>11693, "command"=>"/usr/bin/ruby1.8
> \"/home/someuser/someproject/script/bj\" \"run\" \"--forever\"
> \"--redirect=/home/someuser/someproject/log/bj.TheLuggage.development.log\"
> \"--ppid=11445\" \"--rails_env=development\"
> \"--rails_root=/home/someuser/someproject\""}
Have your checked that that log file doesn't have any clues and that
all of those paths are sane? You want to be able to tell the
difference between the task runner thing not even trying to run your
tasks and trying but failing.
Fred
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
