Seems your right, quick test : fab -H dns1 dns_restart [dns1] Executing task 'dns_restart' [dns1] sudo: service bind9 restart [dns1] out: sudo password: * Stopping domain name service... bind9 [dns1] out: ...done. [dns1] out: * Starting domain name service... bind9 [dns1] out: ...done.
Done. Disconnecting from dns1... done. wernerg@admin:/opt/git/bin$ fab -H dns1 dns_restart [dns1] Executing task 'dns_restart' [dns1] sudo: service bind9 restart [dns1] out: * Stopping domain name service... bind9 [dns1] out: ...done. [dns1] out: * Starting domain name service... bind9 [dns1] out: ...done. First time it prompts me for a password - why? As far as I understand Fabric should be able to handle this? Give the password and then the script runs without a hitch on re-runs afterwards. On Thu, Dec 1, 2011 at 6:59 PM, Paul Hoffman <[email protected]> wrote: > I suspect that most of the time, sudo is being run when a password is > needed (that is, there hasn't been a recent sudo from that user), but > in the failure times, sudo is not prompting for a password because it > isn't needed. > > Does Fabric itself assume that a password is needed every time? > > --Paul Hoffman >
_______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
