X-Spam-Check-By:	sourceware.org
Message-ID:	<43E93686.1060202@kinobe.com>
Date:	Tue, 07 Feb 2006 19:08:38 -0500
From:	Jonathan <cygwin DOT com AT kinobe DOT com>
User-Agent:	Thunderbird 1.5 (X11/20051201)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
CC:	ericblake AT comcast DOT net, vendors AT tpsoft DOT com
Subject:	1.5.19: Solution: cannot create temp file for here document: Permission denied
X-Declude-Sender:	cygwin DOT com AT kinobe DOT com [192.168.1.101]
X-Declude-Spoolname:	D364701930000001d.smd
X-Declude-Note:	Scanned by Declude 3.0.5.20 (http://www.declude.com/x-note.htm) for spam.
X-Declude-Scan:	Score [0] at 19:07:41 on 07 Feb 2006
X-Declude-Tests:	Whitelisted
X-Country-Chain:
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Hi all,

I recently set up cygwin on a Windows 2003 box with NTFS file permissions. I 
encountered the same problem as mentioned in this thread:
http://www.cygwin.com/ml/cygwin/2005-07/msg00732.html

To sum up the issue: Upon ssh login I received the following error message:

-bash: cannot create temp file for here document: Permission denied

One thing I noticed was that looking at the permissions for the tmp folder under 
the cygwin directory, the permissions for [SERVER]\Users were marked as "Special 
Permissions" rather than the usual set of permissions (e.g., Full Control, 
Modify, etc.). Even though the user seemed to have all of the necessary 
permissions when clicking the Advanced button, I chose to override these 
permission by clicking the  "Modify" checkbox (and additionally all of the 
permissions that get auto-selected when you choose "Modify") and the error 
message went away.

One particular detail about our installation that might be involved in this 
problem: The original installer of cygwin on this particular machine did not 
give [SERVER]\Users "Modify" permission on the cygwin directory. We only added 
them after the install. It's possible that adding these permission to the cygwin 
directory after the install doesn't cascade them in the same way as having them 
there before install does.

I hope this helps,

Jonathan Gordon.
---
[This E-mail scanned for viruses by Declude EVA]


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

- Raw text -