I'm able to easily duplicate this (on EC2 mid-afternoon anyway) with:

COMMAND="sleep 3000" cap invoke

I'll see the sleep disappear from the server, but cap will sit there
indefinitely.

So I guess 2 problems here, one I can't keep the connection alive, and
two, the connection doesn't know its no longer alive.

Matt


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to