Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Fri, 26 Aug 2005 18:09:22 -0400 (EDT)
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
Reply-To: cygwin@cygwin.com
To: Joshua Daniel Franklin <joshuadfranklin@gmail.com>
cc: cygwin@cygwin.com
Subject: Re: crontab (Attn: FAQ maintainer)
In-Reply-To: <cb51e2e0508261438514b7d6c@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.0508261807410.28254@slinky.cs.nyu.edu>
References: <430B3DCD.857CD22E@opgc.univ-bpclermont.fr>    <Pine.GSO.4.63.0508231423170.27271@slinky.cs.nyu.edu>    <430DE5CC.9A9A3629@opgc.univ-bpclermont.fr>   <Pine.GSO.4.63.0508251144150.28254@slinky.cs.nyu.edu>    <430F1B23.EA7DA18@opgc.univ-bpclermont.fr>   <Pine.GSO.4.63.0508261015570.28254@slinky.cs.nyu.edu>    <430F33F5.3BBBC098@opgc.univ-bpclermont.fr>   <430F3703.6261D1BB@dessent.net>    <Pine.GSO.4.63.0508261227370.28254@slinky.cs.nyu.edu>  <cb51e2e0508261438514b7d6c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 26 Aug 2005, Joshua Daniel Franklin wrote:

> On 8/26/05, Igor Pechtchanski wrote:
> > On Fri, 26 Aug 2005, Brian Dessent wrote:
> >
> > > The answer is in the link that Igor gave you.  This FAQ perhaps should
> > > be split up into two questions, or at least be made more clear that
> > > there are two problems being addressed in the answer.
> >
> > FWIW, I second this suggestion.  Joshua, can we have two questions: "Why
> > don't Cygwin services work?" and "Why can't Cygwin services access network
> > shares?" instead of the combined one?
>
> Now that it's in DocBook, it would be a pleasure. :)
>
> > > The first part about user/system mounts is not your problem.  Read the
> > > second part of the answer, and read the 'ntsec' part of the manual for
> > > the full explanation.
> > ---------------
> > > When cron runs your job, it is running as SYSTEM impersonating the user
> > > account that owns the crontab.  During impersonation, the user's
> > > password is not available and so non-public network shares are not
> > > available.
> > ---------------
> > Now, the marked part above, IMO, looks good enough to put almost verbatim
> > into the second question.  Opinions?
>
> Sure. I'll probably leave in the link to using-ntsec.html

Yes, that's what I meant, in addition to what's already there about ntsec
(basically everything after the code section).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

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

