The login server of my company is rather paranoid I guess. I can' t use that server as gateway for tunneling to production servers.
# Term 1 ssh -N 7845:prod.server:22 -L jake@login1 # Term 2 ssh [email protected]:7845 will fail. Term1 returns something like Channel 2: open failed: administratively prohibited: open failed I googled a lot, found out this is the reason that failed capistrano. Then I learned ssh-agent stuff, managed getting this to work: ssh jake@login1 ssh [email protected] This command will give me a fake terminal. Saying something like: Pseudo-terminal will not be allocated because stdin is not a terminal. executing `hostname` will return the correct answer. Is there anyway that I can let capistrano deploy my humble code this way? -- -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en --- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
