If you need to run commands in the background, a message queue is the way to go. Resque and resque-status offer you some ability to check in on the progress of background jobs, though if you're shelling out you'd still need to have some way for your background worker to monitor the (forked) process, which depends on what exactly it is you're doing.
On Feb 10, 2010 12:48 AM, "Saurabh Peshkar" <li...@ruby-forum.com> wrote: Hi Marnen, I am trying to determine whether the system command which I had run is running properly on the console or not, through ruby code. Thanks, Saurabh -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed... -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
