X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: Yes, hits=5.8 required=5.0 tests=AWL,BAYES_00,BOTNET,RCVD_IN_DNSWL_NONE,TW_HR X-Spam-Check-By: sourceware.org From: "Jeffrey J. Kosowsky" MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Message-id: <19740.3442.794266.228950@consult.pretender> Date: Wed, 29 Dec 2010 23:41:22 -0500 To: cygwin@cygwin.com Subject: Why are some default Windows environment variables not set when logging in via ssh? Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com When I run a cygwin bash terminal directly from Windows, I get all the standard Windows environment variables properly set. However, when I login in via ssh, some are properly set (e.g., $USERPROFILE, $ALLUSERSPROFILE, $HOMEDRIVE) but others are unset (e.g., $TEMP, $TMP, $APPDATA, $LOCALAPPDAT, PROGRAMFILES). - Is this just a weird artifact of the fact that sshd is run by cyg_server rather than by the actual user (which perhaps explains why the variable $USERNAME is set to cyg_server)? - Even so, why would PROGRAMFILES not be set right since that is presumably not user-dependent? - Is there any logic behind which variables work and which ones don't? - Is there any way to "fix" this so that the variables are set "normally"? (I could kluge this by setting them manually in my bashrc but I would prefer for them to be set right automatically) THanks -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple