Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Date: Wed, 29 Sep 2004 21:53:22 -0700 From: Joshua Daniel Franklin Reply-To: Joshua Daniel Franklin To: Cygwin List Subject: Re: Crontab issue In-Reply-To: <6.1.0.6.0.20040909142537.03dc3838@pop.prospeed.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4DE70F2A7A19D511B7EC00D0B77E7C31F13E7D AT UBANYEXCH> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040909142537 DOT 03dc3838 AT pop DOT prospeed DOT net> X-IsSubscribed: yes On Thu, 09 Sep 2004 14:29:16 -0400, Larry Hall wrote: > Access to network shares seems to come up allot in the context of Cygwin > services. Maybe it would be good to add something to the FAQ on this. > What do you think Joshua? See how this does: Some Cygwin services normally run as the SYSTEM user, which has certain limitations. Under the Windows authentication scheme, the SYSTEM user cannot access network shares that require authentication. For more information, see `http://cygwin.com/cygwin-ug-net/ntsec.html'. Workarounds include using public network share that does not require authentication (for non-critical files), or running the service as your own user with `cygrunsrv'. -- 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/