@@ -69,6 +69,29 @@ Note that is there is EventMachine present and running, will return an instance of Rufus::Scheduler::EmScheduler (leveraging EventMachine). +== scheduler.join + +Note that if you have a tiny script like this one : + + require 'rubygems'; require 'rufus-scheduler' + + scheduler = Rufus::Scheduler.start_new + + scheduler.at 'Thu Mar 26 07:31:43 +0900 2009' do + puts 'order pizza' + end + +And you run it, it will exit immediately. + +If you place + + scheduler.join + +at then end of it will make the current (main) thread join the scheduler and prevent the Ruby runtime from exiting. + +You shouldn't be exposed to this issue when using EventMachine, since while running EM, your runtime won't exit. + + == block parameters Scheduled blocks accept 0 or 1 parameter (this unique parameter is the job README.rdoc @@ -41,7 +41,6 @@ module Scheduler # When the job is actually running, this attribute will hold the # thread in which the job is running. - # Can be used to determine if a job is actually running. # attr_reader :job_thread lib/rufus/sc/jobs.rb 6a8c1eded989c6436d1e87e93c00ef23cca705b0 John Mettraux jmettraux@gmail.com http://github.com/jmettraux/rufus-scheduler/commit/77a43e6ee84d1b4923816586a6f2c2f848f92e74 77a43e6ee84d1b4923816586a6f2c2f848f92e74 2009-11-04T18:01:37-08:00 2009-11-04T18:01:37-08:00 added note about Scheduler#join 0af82c84821939d9a8ea3ba3bb10f9b228d0973a John Mettraux jmettraux@gmail.com