I was able to work around a similar issue by running the sudo command, and in the /etc/sudoers file making sure that no password is prompted for the executable
Hope this helps, John George On Dec 18, 12:17 pm, Tony Davis <[EMAIL PROTECTED]> wrote: > I have the same problem, any solutions? > > On Dec 7, 1:45 pm, David Adams <[EMAIL PROTECTED]> wrote: > > > > > I love the idea of Capistrano, but it's not working for me in my > > environment. I hope there's something simple I'm missing, but I'm not > > sure. Here's the situation: > > > I don't have root on the app servers I need to automate. For each > > application, we have a Unix user for which I don't have the password, > > but which owns all the appropriate application files. To administer an > > app, I log in with my personal account, and then I "sudo su - svcuser" > > to become the service account, run whatever commands I need, then > > logout twice. > > > Unfortunately, my limited understanding of Capistrano has failed me at > > this point. eg: > > > task :sudo_test do > > sudo "su - svcuser" > > run "whoami" > > end > > > I get prompted for my password, but then I get the shell prompt of the > > svcuser's shell as output and everything hangs. > > > Any ideas? Let me know if you need more information. I appreciate the > > help. > > > David Adams- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
