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
Message-ID:	<cb51e2e0508261438514b7d6c@mail.gmail.com>
Date:	Fri, 26 Aug 2005 14:38:13 -0700
From:	Joshua Daniel Franklin <joshuadfranklin AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: crontab (Attn: FAQ maintainer)
In-Reply-To:	<Pine.GSO.4.63.0508261227370.28254@slinky.cs.nyu.edu>
Mime-Version:	1.0
References:	<430B3DCD DOT 857CD22E AT opgc DOT univ-bpclermont DOT fr> <Pine DOT GSO DOT 4 DOT 63 DOT 0508231423170 DOT 27271 AT slinky DOT cs DOT nyu DOT edu> <430DE5CC DOT 9A9A3629 AT opgc DOT univ-bpclermont DOT fr> <Pine DOT GSO DOT 4 DOT 63 DOT 0508251144150 DOT 28254 AT slinky DOT cs DOT nyu DOT edu> <430F1B23 DOT EA7DA18 AT opgc DOT univ-bpclermont DOT fr> <Pine DOT GSO DOT 4 DOT 63 DOT 0508261015570 DOT 28254 AT slinky DOT cs DOT nyu DOT edu> <430F33F5 DOT 3BBBC098 AT opgc DOT univ-bpclermont DOT fr> <430F3703 DOT 6261D1BB AT dessent DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0508261227370 DOT 28254 AT slinky DOT cs DOT nyu DOT edu>
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id j7QLcNtP005707

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

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