Stewart, I'm afraid I can't comment, but that's always a good way to diagnose… in the event that you *really* don't care about what happens, you can always suffix the command with a & (ampersand) http://hacktux.com/bash/ampersand -- it will fork the process, and background it - giving you back your terminal, but output wont be written back to you.
You might want to check #nginx and #openssh on Freenode IRC; it might also be worth pastying your init scripts (what OS were you using?) - maybe there's something weird in them, I'd be interested at least to take a look - but I can hardly promise that I can help! - 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
