Hi Brian, You're right - that's a hell of a long time!
I think the problem is that there's no traffic on the wire, I've seen people work around this by doing with he block-form of run() and writing \0 to the channel from time to time to keep it alive; YMMV, if you come up with something reliable, I'd really appreciate a gist with the code; I'd be happy to document it as a workaround. Regarding the long-running (read: never ending) job on the server, if you get a moment please strace it - I have a feeling it'll be stopped because it's stderr/out/in have disappeared, you could try redirecting the output and see if that makes the job more reliable. Is it really important that you run the job "live" - or could you not connect to the server and see how it's going? Starting the job under any of `nohup`, `screen` or `&` might offer better, more reliable results. (and you could always make another task to check-in, and look at the log again after you started the job?) I hope some of my ideas/suggestions help, looking forward to hearing back from you to see if any of the suggestions make your jobs work out better! - Lee -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
