X-Spam-Check-By: sourceware.org
Message-Id: <6.2.3.4.2.20060207182235.0282d478@mail.tpsoft.com>
Date: Tue, 07 Feb 2006 18:25:26 -0800
To: Jonathan <cygwin DOT com AT kinobe DOT com>
From: Barry Demchak <vendors AT tpsoft DOT com>
Subject: Re: 1.5.19: Solution: cannot create temp file for here   document: Permission denied
Cc: cygwin AT cygwin DOT com, ericblake AT comcast DOT net
In-Reply-To: <43E93686.1060202@kinobe.com>
References: <43E93686 DOT 1060202 AT kinobe DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-PopBeforeSMTPSenders: bdemchak AT tpsoft DOT com,copies AT tpsoft DOT com,vendors AT tpsoft DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

The solution to my variant of this problem ended up being pretty simple.

I was running the Norton utility that guards the trash bin (Norton 
Protected Trash Bin).

For this use, it's toxic.

The solution was to add the entire cygwin directory to the exclusion 
list (in the trash bin's Properties dialog). It would look something 
like: "-c:\cygwin\**".

Keeping Norton's hands off these files makes cygwin not mess up.

Charming.

Does this help you?


At 04:08 PM 2/7/2006, Jonathan wrote:
>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/