I can think of one thing which may be the case: If you SSH via the terminal, some bashrc/bashprofile thingie might run on the server that would not otherwise run in batch mode (noninteractively, which is what your Go code is likely doing).
Try this: ssh -o "BatchMode yes" host sh -c 'echo $VARIABLE_YOU_WANT_TO_CHECK' < /dev/null Then this: ssh -t host sh -c 'echo $VARIABLE_YOU_WANT_TO_CHECK' If there are differences, that is proof of this theory. On 11/03/2019 07.00, Subramanian Sridharan wrote: > Hi guys! > > I would like to know how to keep the environment variables over SSH > using Go. > > I find that several environment variables are missing when I SSH using > Go. > > For instance, the proxy environment variables are not present when I > SSH using Go, but they're present when I SSH using an actual terminal. > > Screenshot from 2019-03-11 12-28-22.png > > > Thanks in advance! > -- > You received this message because you are subscribed to the Google > Groups "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to golang-nuts+unsubscr...@googlegroups.com > <mailto:golang-nuts+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout. -- Rudd-O http://rudd-o.com/ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
