MIME-Version: 1.0
In-Reply-To: <4B16EF31.60102@cygwin.com>
References: <26617039.post@talk.nabble.com> <4B16EE8D.3070905@gmail.com> 	 <26617812.post@talk.nabble.com> <4B16EF31.60102@cygwin.com>
Date: Fri, 4 Dec 2009 09:46:25 +0100
Message-ID: <1ef5a52f0912040046r745bebe5l8c6053d022425c7b@mail.gmail.com>
Subject: Re: Problem with bash script running under NT AUTHORITY\SYSTEM
From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Wed, Dec 2, 2009 at 11:50 PM, Larry Hall (Cygwin)  wrote:
> Remember, SYSTEM is not you.

Unless Louis XIV was a Cygwin user, in which case he might have said

Le syst=E9me, c'est moi!

On Thu, Dec 3, 2009 at 5:02 PM, Almo <> wrote:
>
> Ok, it's that SYSTEM running through cygwin has no access to the disk.
>
> So someone else wrote the script to run in DOS, and we've dropped the idea
> of scripting scheduled tasks with cygwin. Unless I can figure out how to =
get
> SYSTEM access to the disk through it. :)

Perhaps  NT AUTHORITY/SYSTEM should be given access rights to the
appropriate directory (right click, Properties, Security). It's just
an "account" like any other.
I'm somewhat puzzled though. On my machine, SYSTEM has full access to
C:. Is this a network drive ?

Csaba
--=20
Life is complex, with real and imaginary parts

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