General discussion about Chef

[chef] Execute resource - keeping SSH_AUTH_SOCK environment variable


Chronological Thread 
  • From: Joe Van Dyk < >
  • To: chef < >
  • Subject: [chef] Execute resource - keeping SSH_AUTH_SOCK environment variable
  • Date: Tue, 4 Jan 2011 01:33:39 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=IGCvEBtz3n2SToUP5yT1rdSH27HeHCfhCX1TuGL6EEPZCFZ+6k9WL/IAUdW5ynzHNZ /mSaOQAFTlijhZZynETYaLtlmPVEuWXKzf9oEuKFf3mv4f94kbX0KtbBz5bM2WS1T0Ir XDQIAf3rpoS7ZfGfd+zNGcI1KA5mrb5RxtKJU=
If I'm logged on as user1 with my SSH_AUTH_SOCK environment variable
set, and I run chef-solo which runs a command as user2, how can I have
user2's command be able to access the SSH_AUTH_SOCK?

Joe

Archive powered by MHonArc 2.6.16.

§