From: Xeno Campanoli Date: 2009-06-06T04:37:38+09:00 Subject: Re: Problem with cronjob and ruby script Matthew Lagace wrote: > Tried everything in here and same problem. What I've noticed though this > version of Ubuntu (Feisty Fawn 7.04) which I know is outdated messed up > all the paths for ruby and rubygems. > > Hassan Schroeder wrote: >> On Fri, Jun 5, 2009 at 9:38 AM, Kyle Schmitt >> wrote: >> >>>> 5,20,35,50 * * * * export JAVA_HOME=/usr/local/jdk1.6_013 �&& >>>> /usr/bin/jruby - S blah blah >>> Hassan, just a note, you don't need the "export" part of the line :) >> Force of habit; in this example, no, but if a subsequent part of the >> entry spawns a new shell, I think it's necessary. >> >> I think. Will have to revisit that sometime, but not today :-) > Hey, does this thread have anything to do with the Bourne-shell usage bias which first manifested itself for me in at last year? In other words, if you use a shell, any shell, in at you get sh, not bash, the former being considered lighter weight and perhaps somehow safer and more standard, but on the other hand breaks things like some commands you are used to in some syntax in Bash. For instance, you must do the following to export: x=y export x because export x=y does not work in sh. ???