[Capistrano] Re: Changes to remote command invocation in 2.1.0

[Jamis Buck]

Before Capistrano 2.1, every command was executed in a pseudo-terminal (pty) environment. The drawback of this is that it prevented (in most configurations) your default .bashrc from being loaded. As of cap 2.1, the default is for commands to _not_ execute in a pty. This means that your .bashrc (or .bash_profile, or whatever) WILL be loaded for every command you execute. The drawback is that some commands don't want to work interactively without a pty. Yours was the first I've seen of something trying to write binary data to stdout without a pty, but the clue was when you said it worked under 2.0, and not under 2.1.

Anyway, glad it worked.

- Jamis

On Feb 25, 2008, at 5:35 PM, Bill Kirtley wrote:

Yup.  That fixed it.  What's that about anyway?

(Thanks for the quick and helpful response!)


What happens if you set the following in your deploy.rb:

  default_run_options[:pty] = true

?

- Jamis

On Feb 25, 2008, at 5:07 PM, Bill Kirtley wrote:

>
> Hello-
>
> My application uses a service that runs in the background.  It's
> started and stopped with a rake task, and the service itself is
> implemented in ruby and uses a familiar fork scheme.
>
> Starting and stopping the process works just fine when invoked by
> capistrano 2.0.0 but not with 2.1.0.
>

> seeing output the child sends to stderr.  Stopping cap with ^c does
> stop capistrano and the server process keeps running.
>
> It does this regardless of whether I specify 'nohup' in the 'run'
> command.  If I don't have nohup with 2.0.0, the server process dies
> when the parent exits.
>
> I'm running on Mac Leopard, ruby 1.8.6, and controlling which cap I
> use via the `cap _2.1.0_ deploy:whatever` syntax, FWIW.
>

> if anyone here knew what might have changed with regard to the
> environment commands are run in.
>
> Thanks in advance for any pointers,
> -Bill Kirtley
> >



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

On Mon, Feb 25, 2008 at 7:22 PM, Jamis Buck <[EMAIL PROTECTED]> wrote: > When I run it with 2.1.0 the cap process never finishes, and winds up > I'm going to start wading through the capistrano sources, but wondered

smime.p7s
Description: S/MIME cryptographic signature