X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=cuBa7nuxUH9gn3eUrMMTB4Zf/F98WBpzz7wv5WRdiVF
	XvyTv6ZGjVeWPrA7n81jJxNqZRwIcJeZMdjQw3ehIoXip3fqRv/AqlVi4AtvqShd
	JTyk5oT/G5f4vTeIBo/fRxTSmumnhkZ4ZJDnkyRfFx0g7HTp4b8HECEqVcimh4tc
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=4krjI9LMm56R1gs8SrOKPSQycHk=; b=qFXHQTlh6Hlb3dzNX
	ETCkdEf3EZN058sQpYZEKVV5fBi8628zKdCN7/6fN2dc1pb0wU+FtUoJw91DTlDF
	0p4/EhUa9Snnaj7MljyxK2YDy85LFlsqveLxTnn+En2SbAnD5TWvcK+FgH96sCYm
	OxZlRDt2Q+73zr4Sdp51zQg5m0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-ig0-f182.google.com
X-Received: by 10.50.108.68 with SMTP id hi4mr165341igb.38.1421176343207;        Tue, 13 Jan 2015 11:12:23 -0800 (PST)
From: "cyg Simple" <cygsimple AT gmail DOT com>
To: <cygwin AT cygwin DOT com>
References: <20150107174122 DOT GB4190 AT calimero DOT vinschen DOT de> <20150108171825 DOT GB15791 AT calimero DOT vinschen DOT de> <8761cez7qi DOT fsf AT Rainer DOT invalid> <20150112103834 DOT GA15213 AT calimero DOT vinschen DOT de> <loom DOT 20150113T124708-54 AT post DOT gmane DOT org> <20150113125648 DOT GV15791 AT calimero DOT vinschen DOT de> <loom DOT 20150113T135909-484 AT post DOT gmane DOT org> <20150113135339 DOT GW15791 AT calimero DOT vinschen DOT de> <loom DOT 20150113T150342-521 AT post DOT gmane DOT org> <04ae01d02f3e$7eb2f6c0$7c18e440$@gmail.com> <20150113154719 DOT GX15791 AT calimero DOT vinschen DOT de>
In-Reply-To: <20150113154719.GX15791@calimero.vinschen.de>
Subject: RE: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
Date: Tue, 13 Jan 2015 14:12:35 -0500
Message-ID: <074901d02f64$e54a6f00$afdf4d00$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="utf-8"
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t0DJCeuh027984

> From: Corinna Vinschen
> 
> On Jan 13 09:37, cyg Simple wrote:
> > > -----Original Message-----
> > > From: Achim Gratz
> > >
> > > Corinna Vinschen  writes:
> > > > Which means what for the Cygwin DLL?  Dropping TMP/TEMP from the
> > > > merged Windows env?  It makes sense, I think.  Of course, there
> > > > will be others...
> >
> > My process is dependent on the fact that TMP/TEMP have in/out
> > rewriting of strings from POSIX to WINDOWS so please leave it as is.
> 
> You're missing something here.  What we're talking about is a merge of the

Correct, I was missing this key point.

> user's Windows default environment at the time of a user context switch (for
> instance, logon via ssh).  In that case, "leaving it as is"
> today would mean to *drop* TMP/TEMP from the environment, because that's
> what ssh does anyway.  Ssh drops almost everything from the environment,
> before exec'ing the child process.  And that's a good thing, because the
> environment (e.g. LOCALAPPDATA, USERPROFILE, etc) would otherwise reflect
> the settings of the user running the sshd service, not the settings of the user just
> logging in.
> 

Shouldn't these be removed during the startup of sshd?  Then the child process would setup the variables during the login process?

> The new functionality we're talking about here is that the next Cygwin would
> "resurrect" the Windows environment setting for the child process started by
> sshd.  And these settings would be the one for the user just logging in.  This
> would help some Windows applications which otherwise choke if these
> Windows environment variables are missing.

Ack.

> 
> Having said that, TMP/TEMP have the downside of being used by POSIX and
> Windows applications alike.  Therefore these variables usually are converted
> from Windows to POSIX and vice versa on the fly.

This is what I was referring to earlier.

> 
> However, whether it makes sense to set TMP/TEMP in a ssh logon session or a
> cron session is questionable.

Ack.  The environment tends to be empty on cron in *nix so I agree.  The logon process tends to be what sets the variables, however with Cygwin sshd we need to logon to a new user; would remote desktop protocol provider API help?

http://msdn.microsoft.com/en-us/library/dd919947(v=vs.85).aspx

--
cyg Simple



--
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