X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 17 Apr 2008 18:00:45 -0700 From: Gary Johnson To: cygwin@cygwin.com Subject: environment variables and ssh logins Message-ID: <20080418010044.GE17899@suncomp1.spk.agilent.com> Mail-Followup-To: cygwin@cygwin.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: SunOS suncomp1 5.8 sparc User-Agent: Mutt/1.5.17 (2007-11-01) X-IsSubscribed: yes 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 I have several environment variables defined in the Windows Control Panel -> System -> Advanced -> Environment Variables -> System Variables list on my Windows XP box. If I run a Cygwin bash login shell locally on this machine, I can find all those environment variables in the output of the env command. However, if I ssh to the same machine, several of those environment variables are missing from my environment. For example, PATH is in both environments and is the same except for the extra :/bin component in the ssh version, and "CYGWIN=ntsec" is in both. However, PYTHONPATH is in the local environment but not in the ssh environment. Why are some but not all the environment variables defined in the System dialog inherited by ssh logins? Thanks, Gary -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/