Anibal,
What is the behavior when you try with nohup? Using nohup is the
recommended way to fire off long-running processes with Capistrano:
run "nohup #{current_path}/script/runner SomeService.run &"
Also, if the invocation itself has any complexity at all, you might be
better off encapsulating it in your own script, first, and invoking it
that way:
run "nohup #{current_path}/script/my_script &"
- Jamis
On 2/9/09 4:45 PM, Aníbal Rojas wrote:
> Hello,
>
> As part of my deployment process I want to start a script/runner
> and I don't want to wait for it to end its execution, as it is a
> pretty long process , off course with a Capistrano task.
>
> It works, but it never returns from the run " ... script/runner ...
> " invocation
>
> Breaking the execution of the Capistrano task with Ctrl-C doesn't
> affect the running process, but it is kind of ugly and I want to
> properly finish everything and call hooks, etc.
>
> I am not sure about the fine details of the ssh stuff under the
> hood, and I tried using nohup ... &, redirecting the stdin and error,
> and nothing made any difference run " ... script/runner ... " blocks
> without returning
>
> Thanks in advance,
>
> ---------------------------------------- ----------------
> Aníbal Rojas
> http://hasmanydevelopers.com (work)
> http://rubycorner.com (community)
> http://anibal.rojas.com.ve (personal)
>
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
