Ruby on Rails

Colin Law wrote in post #1119927:
> On 29 August 2013 11:33, Shawn h. <lists@ruby-forum.com> wrote:
>> Dear all,
>> I am developing a web harvesting server which requires regularly
>> website parsing. Since I use Mac 10.8 as my development environment, I
>> try to use Launchd to routinely wake up my parser. My parser was a bash
>> script which has only two lines:
>> 1. cd $HOME/ProjectFolder
>
> Just a thought, is $HOME valid when this is run?
>
> Colin

Thanks for reply. I checked the path and it is ok. I test directly with
no variable and the result is identical.
I did some other experiments. In the batch script, I can successfully
run
bundle exec rake --version or bundle exec rake -h
However, when I run bundle exec rake -T, it would produce exact
segmentation error as follows:
crontab-test.sh: line 6: 29245 Abort trap: 6
/usr/local/Cellar/ruby/2.0.0-p195/bin/bundle exec rake -T >>
/tmp/cron-test.out
/usr/local/Cellar/ruby/2.0.0-p195/lib/ruby/gems/2.0.0/gems/mysql2-0.3.13/lib/mysql2/mysql2.bundle:
[BUG] Segmentation fault
ruby 1.8.7 (2012-02-08 patchlevel 358) [universal-darwin12.0]

I don't understand why bundle exec rake would encounter errors for
mysql2 bundle, especially when it reports ruby 1.8.7 while I am sure I
use 2.0.0p195. Does it imply when launchd exec the bash script, it has
its own environment which uses ruby 1.8.7?

--
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 unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3dd763af299118e12e8885aa789502f0%40ruby-forum.com.
For more options, visit https://groups.google.com/groups/opt_out.