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:message-id:date:from:mime-version:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=h3qIMarSE3KgDodmP7DjSZ9NBrpazfiASBArrRCDEhi
	GIujftssxJBfhETmRzutGyNlEhzd5ZsfmekkuZoPJvYL/dk+EMmPfeNEZx6eW1+2
	cnZPg8p90aVV9ojtGksAx0qtu5hGwY47+Qks35qsKBBOTUlvmV9eLxKLWjueMOmc
	=
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:message-id:date:from:mime-version:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=s8XwWvOtYaDI7p6jsIXTz3zOAIM=; b=WZNY+FarEC1PenQz6
	h3gADLRYwCrEtvQR/49SMNqZ1pThkzosLcD0bAc0jN1rLVVRsE2DQbv8gRJRslNF
	kB21jvO78R4LHvg4+FBA8aFy6gpHC6Ozyj4GB7dYosWNZIIvKxNJgw3eC8MoVWYu
	dzXDyk+WnShWhnO1c/OPy/OuXQ=
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: Yes, score=6.2 required=5.0 tests=AWL,BAYES_50,MISSING_HEADERS,RCVD_IN_PBL,RCVD_IN_RP_RNBL,RCVD_IN_SEMBLACK autolearn=no version=3.3.2
X-HELO: konqorde.nl
Message-ID: <5241E794.1080506@mailme.ath.cx>
Date: Tue, 24 Sep 2013 21:27:16 +0200
From: bartels <bartels AT mailme DOT ath DOT cx>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130704 Icedove/17.0.7
MIME-Version: 1.0
CC: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Confused about several issues with setting up cron
References: <B8D164BED956C5439875951895CB4B2211449DC8 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> <523F133D DOT 2060806 AT mailme DOT ath DOT cx> <523F48E1 DOT 8070905 AT mailme DOT ath DOT cx> <B8D164BED956C5439875951895CB4B221145A863 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> <B8D164BED956C5439875951895CB4B2211477D08 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> <5241CBA1 DOT 7000405 AT mailme DOT ath DOT cx> <B8D164BED956C5439875951895CB4B221147AEF5 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com>
In-Reply-To: <B8D164BED956C5439875951895CB4B221147AEF5@WABOTH9MSGUSR8C.ITServices.sbc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 09/24/2013 08:13 PM, KARR, DAVID wrote:
>     15   31593 [main] crontab 8612 fhandler_base::open_fs: 0 = fhandler_disk_file::open(\??\C:\Cygwin\var\cron\tabs\dk068x, 0x8000)
>     21   31614 [main] crontab 8612 open: -1 = open(tabs/dk068x, 0x8000), errno 2


There you go: the process has no write access to your crontab file (C:\Cygwin\var\cron\tabs\dk068x)

Popular advice on this list is that you do not mix posix and windoze permissions.
I have fallen into that trap myself.

- bartels

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