Gary, There's not currently any way to set a timeout on a command. I'd be a little nervous about adding such a setting, because I fear it would set expectations. For instance, suppose you have a timeout on a long-running command. The timeout expires, and Capistrano closes the connection. Would users expect capistrano to also try and abort the command? Would they be surprised to see the command still running on the host after Capistrano times out?
That said, if someone wants to try and roll a patch for Capistrano that implements command timeouts, I'd consider it. Especially if they're able to address the "what happens on the server when a timeout expires" question, unambiguously. - Jamis On 1/29/09 10:25 AM, Gary Richardson wrote: > Hi, > > I'm currently load testing an application and I seem to be crashing > some of my cluster members. They still respond to pings, but when I > try to run commands against them, they hang. I'm assuming this is > because Capistrano is able to connect to the SSH port, but it doesn't > respond. > > For example, cap invoke COMMAND=uptime will sit forever waiting for > the port to respond. > > Is there away to set a timeout for a command? That would make it easy > for me to figure out which hosts were dead. > > Thanks! > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
