You're not posting an actual example of what you're talking about, which makes it quite hard to actually offer advice :) The feature is working for most folks as far as I've seen.
Note that the feature only works for actual prompts Fabric itself handles: sudo and login prompts. Other interactive prompts will still cause Fabric to "hang" waiting for a user, because we cannot reliably detect them. On Fri, Apr 26, 2013 at 11:17 AM, Worker Bee <[email protected]> wrote: > Hi All; > > When I attempt to use --abort-on-prompts and parallel execution, fabric > still hangs on hosts with expired passwords (waiting for user input). I > have tried using: > > env.abort_on_prompts = True > > @with_settings(abort_on_prompts=True) > > and via the command line: > > # fab -P --abort-on-prompts > > None of these work; if a host is encountered that prompts for input, fabric > does not abort. > > I am running fabric 1.6 and paramiko 1.10. > > Has anyone else had this issue? Any ideas would be appreciated! > > Thanks in advance. > Bee > > _______________________________________________ > Fab-user mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/fab-user > -- Jeff Forcier Unix sysadmin; Python/Ruby engineer http://bitprophet.org _______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
