I though using & at the end of the line : nohup bundle exec rake resque:work QUEUE=$2 >/dev/null 2>&1 &
would make it a background task, and nohup prevents it being shutdown when the ssh session ends. This seems to be a fairly common technique. Anyway, I've found a hack which works for me, although I'm not sure why. I added sleep 10 after the nohup call above. Perhaps the resque process outputs something at startup and then fails as the ssh session has been closed. If this is the case, I thought >/ dev/null 2>& should have fixed that. -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to capistrano@googlegroups.com * To unsubscribe from this group, send email to capistrano+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
