P.S.
Solved. Changin "sh" to "nohup" helped. Seems to have been a race
condition where the called script got killed most of the time when cap
logged out, and only sometimes succeeded just before this happened.
Would it make sense to introduce a "nohup" in addition to "run" etc?
Or would it be possible for Capistrano to wait until the command
succeeded?
Tobi
On Fri 2007-11-09 Tobi Reif wrote:
>
> Hi
>
> This task
> run "cd #{latest_release} && sh script/start_watcher"
> fails often when run via cap, and succeeds only sometimes.
>
> It succeds each time when entered directly in a ssh. (with the path
> resolved)
>
> What could I try to make it succeed each time? (wehn uun via cap)
>
> Tobi
>
>
>
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
