Message-Id:	<200504071041.j37Afd4B029351@delorie.com>
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
From:	"Kevin Walker" <kevin AT racbot DOT org>
To:	<cygwin AT cygwin DOT com>
Subject:	Re: 1.5.13/14: Problems with Service running under SYSTEM account
Date:	Thu, 7 Apr 2005 22:28:57 +1200
MIME-Version:	1.0
X-AntiAbuse:	This header was added to track abuse, please include it with any abuse report
X-AntiAbuse:	Primary Hostname - server1057.webserver33.com
X-AntiAbuse:	Original Domain - cygwin.com
X-AntiAbuse:	Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse:	Sender Address Domain - racbot.org
X-Source:
X-Source-Args:
X-Source-Dir:

> Corinna wrote:
>
> Well, it works fine for me.  What you can try is checking the whole
> directory tree from the drive's root dir down to the file for giving
> read (and perhaps execute) permission to SYSTEM or the Administrators
> group.  The last resort is setting CYGWIN=notraverse for the service.

Thanks

I isolated the problem to just one missing permission in the middle of a
rather large directory tree.

Regards
Kevin


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