Hmm! Well, adding :pty => true should have reverted capistrano back to the 2.0 behavior. If you try with cap 2.0, does it work?
cap _2.0.0_ change_password - Jamis On 9/24/07, ken brooks <[EMAIL PROTECTED]> wrote: > > Thanks for responding. > > I tried :pty => true. Same exact result. > > Here is my output. (Names changed to protect the innocent servers). > C:\somedir>cap change_password > * executing `change_password' > * executing "passwd" > servers: ["foo.bar.net"] > Password: > [foo.bar.net] executing command > ** Unexpected failure. Password file/table unchanged. > command finished > command "passwd" failed on foo.bar.net > > > I'm not sure what to do next to debug this. > > thanks, > ken > > On Sep 15, 10:42 am, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > I suspectpasswdon those platforms will fail unless there is a pty > > attached. Try doing this: > > > > run "passwd", :pty => true > > > > - Jamis > > > > On 9/10/07, ken brooks <[EMAIL PROTECTED]> wrote: > > > > > > > > > I have tons of user ids on different machines that I like to keep in > > > sync. > > > > > I was usingcap2.0to executepasswdon a remote host (solaris as > > > well as aix). > > > I would read the data coming back in and send back the appropriate > > > response. > > > Everything worked pretty well. > > > > > Since pulling down 2.1 (Capistrano v2.0.100) I get the following > > > immediately afterpasswdis sent. > > > Unexpected failure. Password file/table unchanged. > > > > > I'm pretty sure you changed a few nuts a bolts about the SSH > > > implementation and the way its creating sessions. > > > Any thoughts on this? > > > > > -Ken > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
