I was hoping to avoid learning another new tool such as monit for now, but maybe it's the only way. I already tried nohup - see original post.
Does anyone know why in particular resque:work is failing to stay running (or how to debug it) ? I can start redis-server and resque-web processes fine from capistrano. On May 12, 7:24 am, Lee Hambley <lee.hamb...@gmail.com> wrote: > I recommend that you don't start jobs 'blind' from capistrano, and instead > use capistrano to control a server-side process monitoring daemon such as > monit, resque even comes with a sample monit file. > > Also if that's not desirable,http://en.wikipedia.org/wiki/Nohup- quoting > from the wiki page: "*nohup* is a POSIX > <http://en.wikipedia.org/wiki/POSIX> command > to ignore the HUP <http://en.wikipedia.org/wiki/SIGHUP> (hangup) signal, > enabling the command to keep running after the user who issues the command > has logged out" (effectively once your capistrano command hangs up, and > finishes) > > - Lee -- * 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
