Hi Mohit, If you mean that the password is cached between successive invocations of the command-line "fab" tool, that's definitely not the case.
You may be experiencing something on the remote end, such as sudo auth caching, which in my experience is often on by default. Your implication below that the 2nd password is effectively ignored would seem to line up with this (especially if you're using an SSH agent to avoid having to enter the login password). If you can give us more info (typically, a pastebin link to a copy of your fabfile as well as the output when you run it) we might be able to pin it down to something more specific. Thanks, Jeff On Sun, Sep 12, 2010 at 9:59 AM, mohit chawla <[email protected]> wrote: > Hi, > > The password argument it seems is disregarded on successive runs after an > initial run. > > fab -H <host-foo> -p <correct-password> works as expected. > > But after that first execution, > > fab -H <host-foo> -p <any-random-string> also works. > > So although it is probably intended to set the environment with the initial > run, and avoid mentioning the password again, I am wondering if it would be > possible to get prompted every time fab is executed ? As mentioned in the > title, Fabric is 0.9.2, running on Debian. > > I am new to fabric, and really liking it, so its very probable that I might > be missing something fundamental. :) > > Thanks. > > _______________________________________________ > Fab-user mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/fab-user > > -- Jeff Forcier Unix sysadmin; Python/Ruby developer http://bitprophet.org _______________________________________________ Fab-user mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/fab-user
