All, I recently ran my first deployment with cap 2.3 and noticed that my custom sudo commands failed because there were being executed by spawning a new shell and passing the command string to it, like so:
/bin/sh -c '<command string from my deploy file>' I was able to resolve this by modifying my /etc/sudoers file and putting "/bin/sh -c" in front of the command. But is there a way to suppress the spawning of a new shell so that it works the way it did in 2.2? Thanks, Wes --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
