On Mon, Apr 2, 2012 at 4:58 AM, Marcelo Araújo Pontes <[email protected]> wrote:
> Unfortunately i haven't been able to fully understand why fabric does > this... if anyone have a good explanation, please share. Interactive I/O requires a pty on the remote end to work best, so Fabric 1.0 changed the pty setting to default to True, as we wanted interactivity to work immediately out of the box. It also fits with the current (possibly misguided, possibly changing in 2.0) philosophy of "behave as close to a by-hand SSH login as possible", which is also why the shell wrapper is on by default. Unfortunately a number of init-style shell scripts misbehave under a not-actually-interactive pseudo-tty and we've never been able to figure out why. The issue for this problem is here: https://github.com/fabric/fabric/issues/395 I've inexplicably managed to keep overlooking this so there's still no FAQ entry; I'm going to go add one right now because that's kind of ridiculous :( Once I put out the next bugfix release the live docs will get updated. Best, Jeff -- Jeff Forcier Unix sysadmin; Python/Ruby engineer http://bitprophet.org _______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
