Ah, silly me, i can just pass '-- -n' to get vagrant ssh to pass -n in, per the docs. (which works)
However, i'm not sure why this is happening in the first place. Not sure if its a vagrant bug, or something wrong on my system. thanks- On Friday, January 10, 2014 4:17:50 PM UTC-8, Ben Hines wrote: > > Anyone ever seen this? > > [0]$ vagrant ssh puppet -c "sudo service iptables stop" > Pseudo-terminal will not be allocated because stdin is not a terminal. > 0 [main] ssh 3524 fhandler_base::dup: dup(some disk file) failed, > handle 0, Win32 error 6 > dup() in/out/err failed > > > > Seems to be the same as this issue: > > > http://stackoverflow.com/questions/5442522/ssh-fails-when-is-being-called-within-windows-service > > However, i'm not sure how to get vagrant to use the '-n' option. > > I'm using the ssh installed by Windows git. > > btw, 'vagrant ssh' works normally, only fails when attempting to run a > command. > > -Ben > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
