Sorry for late response... You were right... After adding export PATH=/usr/local/bin:$PATH
on top of /etc/init.d/thin script, BJ works fine after server restart. Thank you. david Ara Howard wrote: > D. Krmpotic wrote: >> Ara, thank you for the answer... but I don't quite get it... are you >> saying that two Thins are somehow running in different environments? I >> have to say that I don't see how this could be happening, because it's a >> Thin cluster and thus all/both instances stem from the same >> configuration. Please elaborate your thinking a little bit. Thanx again >> > > > i'm not saying the two are running under different environments, i'm > saying that when you re-started them by hand, perhaps at the console, > you may have had a different environment than they were originally > started under - for instance cron or init.d on system boot. may not be > the case - but worth inventigating. > > > > -a -- Posted via http://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 -~----------~----~----~----~------~----~------~--~---
