For a more global fix that will resolve this for any other application
you may have that is attempting to execute sudo remotely, edit your
sudoers file on the remote machine(s) via visudo. Search for
'Defaultsrequiretty' and comment it out.
On Jun 27, 1:56 pm, Jamis Buck [EMAIL PROTECTED]
You need to tell cap to create a pty for each process:
default_run_options[:pty] = true
Annoying, but some commands that have interactive components (like
sudo) won't run if they aren't run with a tty.
- Jamis
On Jun 27, 2008, at 2:20 PM, Jamie Orchard-Hays wrote:
I'm getting this
Thanks, Jamis!
Jamie
On Jun 27, 2008, at 4:32 PM, Jamis Buck wrote:
You need to tell cap to create a pty for each process:
default_run_options[:pty] = true
Annoying, but some commands that have interactive components (like
sudo) won't run if they aren't run with a tty.
- Jamis
Incidentally, if you want to run without a pty in general (which is
handy, because then your .bashrc will be loaded for each command), you
can specify :pty = true on specific commands to force those to use a
pty:
sudo foo, :pty = true
- Jamis
On Jun 27, 2008, at 2:42 PM, Jamie
