Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Fri, 2 Aug 2002 17:41:45 -0700 (PDT)
Message-Id: <200208030041.g730fjK06825@orngca-mls02.socal.rr.com>
To: cygwin AT cygwin DOT com, djordan AT augustmail DOT com
Subject: Re: WinXP upgrade breaks cron mapping
References: <54360-2200285217436170 AT M2W089 DOT mail2web DOT com>
Reply-to: d DOT l DOT dwiggins AT computer DOT org
From: Don Dwiggins <d DOT l DOT dwiggins AT computer DOT org>
In-Reply-To: "djordan@augustmail.com"'s message of "Fri, 2 Aug 2002 13:43:06 -0400"
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 35

djordan AT augustmail com writes:
> I've just upgraded cygwin to the latest releases.  No change in behavior.

> I've also cron'ed just the net use command and captured these error
> messages:

> System error 5 has occurred.

> Access is denied.

> I'd really appreciate any help...

Unfortunately, I can't offer much.  I'm running a cron job (under my domain
user account) that successfully does a net use (with my user name and
password) under Win2000.

Just a thought: try scheduling the same or equivalent job under the Windows
Task Scheduler, and see if you get the same behavior -- I'd suspect that you
would, and that it's some kind of security change in Win XP from NT/W2K.  If
so, you might have some luck shopping the problem on the appropriate
newsgroup.

> I realize the cron is running under SYSTEM account and that's why I have to
> manually map drives within my cron scripts.  

Actually, your script runs under your user ID, but with restricted
permissions vis a vis the network; try doing an "id" in the cron script and
compare the output with what you get from doing it in a bash window.

Good luck,
-- 

Don Dwiggins			 "The truth will make you free,
d DOT l DOT dwiggins AT computer DOT org         but first it will make you miserable"
                                  -- Tom DeMarco


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/